01
Line the numbers up
Orders checked against payouts, fees and refunds on a schedule, with the ones that do not match shown to you rather than averaged away.
Is this for me?
Four problems this work is for.
None of these show up in a design review. They happen in the gaps between systems, which is why they survive a redesign.
The month that will not close
Payouts, refunds and fees need a spreadsheet and an afternoon before anyone can say what the month actually was.
Discounts that cost more than you meant
Codes, automatic discounts and app rules stacking in ways nobody planned when they were switched on.
Tax that disagrees with itself
The store, the invoice and the accounting software each work out a slightly different number for the same order.
Refunds that went nowhere
Money returned to a customer that never showed up in the records you plan the business from.
What we do
What the work actually is.
02
Check the discounts
Every live discount, code and app rule listed, and the combinations that can stack found before a customer finds them.
03
Tax and rounding
Where the store, the invoice and the books disagree, and which one is right. It is usually a rounding rule or a setting nobody remembers changing.
04
A record you can trust
One place the numbers are correct, and a written note of what was wrong so it does not come back next quarter.
Interactive example
A refund, and the payout that follows.
Refund the return, then watch the payout arrive and the check run against the order behind it. A fee applied twice shows up as a flagged line, not a surprise at month end.
A delivered order, one item back, and the payout that follows. The ledger check runs on its own.
Ready
Each step the order takes lands here, with the system it happened in.
Next
The order starts moving when the demo is in view.
Stock
available to sell| Item | Warehouse | Shop |
|---|---|---|
| Field jacket | 7 | 1 |
| Linen shirt | 11 | 3 |
Customer
Maya’s phoneNothing yet. Texts and emails land here as they are sent.
Ledger
Order #1045- Order2 items
- Refundnone
- Feespending
- Payoutpending
- Checkruns when the payout lands
A worked example. The store, the order and the timings are scripted for the demo.
How it runs
We look before we price.
01
Look
We pull the numbers and find the size of the gap before quoting. You keep that either way.
02
Explain
A written account of what is not adding up and why, in language you could hand to your accountant.
03
Fix
The settings, rules and connections corrected, and shown to you before they go live.
04
Check again
A repeating check so the same gap shows up as a number rather than as a surprise at year end.
Pricing
Small jobs $250–$750
Larger work is quoted after a short call, because the price depends on how many systems are involved. You get a written scope and a firm price before anything starts.
Questions
What store owners ask.
Find out what the gap actually is.
We look before we quote, and you keep what comes out of it either way.
Related reading