A business selling in a shop and online gets two reports and two reconciliations. How to unify numbering, stock, refunds and bank reconciliation into one report.
Key takeaways
- Two payment providers are fine; two sources of documents are not. That is the first decision.
- Stock is what breaks first: a shop sale that does not decrement the website produces overselling.
- A cross-channel refund - bought online, returned in store - needs a written procedure, not improvisation at the till.
- One report summarising both channels is the measure that proves the unification actually happened.
A business selling both in a physical shop and on a website usually ends up with two separate worlds: a terminal and till in the shop, clearing and a plugin on the site, two reports, two reconciliations and sometimes two systems issuing documents. Unifying them is not a large technology project - it is a series of decisions about who owns what.
What is usually duplicated, and what must be single
| Component | Common state | What is right |
|---|---|---|
| Payment provider | One for the shop, one for the site | Two is fine, if reconciliation is defined |
| System issuing documents | The till issues, and the plugin issues | One only, or numbering splits |
| Product catalogue | A list in the till, a list on the site | One source, from which the other updates |
| Stock | Counted in store, guessed online | One source, updated automatically |
| Customer record | Anonymous in store, identified online | A shared identifier - phone or email |
| Sales report | Two reports added up by hand | One unified report, broken down by channel |
| Bank reconciliation | Per provider | Per account, with a channel breakdown |
The second row is the critical one. Two systems issuing documents mean two numbering series, which is exactly why your accountant asks for an explanation at year end. Managing numbering itself is covered in invoice numbering and series control.
The four decisions that sort this out
- Who is the source of documents. One system issues; the other reports into it. Anything else creates duplication.
- Who is the source of stock. Usually the system managing the physical shop, because that is where stock is touched.
- Who is the source of the customer. Usually the CRM or the invoicing system, with a phone number as the identifier.
- Where the unified report lives. A spreadsheet works at first, as long as it fills itself.
None of these needs a new system - they need you to decide. Most of the mess in two-channel businesses comes from nobody settling who is master, which leaves both systems "right".
What about a cross-channel return?
A customer who bought online and comes to return in store is the case that exposes the gaps. You need a written procedure, because there is no time to think at the till:
- How the transaction is identified - order number, invoice, or a lookup by phone.
- Who refunds - the till or the website system. The answer decides which card the money returns to.
- What happens to stock - the item returns to shop stock, even if it shipped from a warehouse.
- Which document is issued - a credit note, and from which system.
- What you tell the customer about refund timing - which depends on the provider, not on you.
The simple rule: a refund should return to the same payment method and the same transaction, so ideally whichever system cleared it also refunds it. "We gave cash back" looks convenient and creates a gap between reports.
What a minimal unified report looks like
You do not need BI. You need one table filled daily with six columns: date, channel, transaction count, gross amount, refunds, net amount. If it fills automatically, excellent; if somebody pastes two files into it weekly, that also works, as long as it happens.
What that report exposes within a month:
- A channel with a far higher refund rate that you did not know about.
- Days when the shop sells and the site does not, and the reverse - useful for stock and shifts.
- A gap between gross and what reached the bank, usually fees and occasionally a fault.
How to actually do it, in four weeks
No project needed. This plan works in a live business without pausing sales:
- Week 1 - map. Write down which system issues documents in each channel, where stock lives, and who identifies the customer. Only write; change nothing.
- Week 2 - pick masters. Choose one system for documents and one for stock, and record the decision where everyone can see it.
- Week 3 - connect the easy part. Usually that is linking clearing to the document system, and one-way stock updates.
- Week 4 - build the unified report and run it for a week alongside the old method, to confirm the numbers agree.
The step people skip is the first, and it is the one that saves most of the pain. Half an hour of mapping usually reveals two systems nobody knew were issuing documents in parallel.
When the shop and the site sell the same item
This is the classic overselling case, and it has three practical answers depending on how connected you are:
| Situation | What to do | The price |
|---|---|---|
| No connection between systems | Hold separate stock for the site - a reserved quantity not sold in store | Less efficient, but safe |
| One-way connection | The shop is master, the site updates from it | A short update lag |
| Two-way connection | One source, both channels writing to it | Best, and the most maintenance |
Most small businesses need the first row, not the third. Reserved web stock is an unsophisticated solution that prevents most overselling at zero cost.
What not to do
- Do not run two providers without deciding who issues documents. That is the most expensive duplication.
- Do not manage stock in two places and rely on a manual end-of-day sync.
- Do not let the till issue a manual document when the system is down, without a procedure to complete it afterwards.
- Do not defer reconciliation to month end with two channels running - a gap compounding from two sources is hard to unpick.
Sources
Frequently asked questions
Can I work with two payment providers?
You can, and it is common - a physical terminal from one and online clearing from another. The condition is that reconciliation is defined: knowing which money comes from whom, when, and into which account. What to avoid is two sources issuing documents, because that splits numbering.
How do I prevent overselling between shop and site?
One stock source and automatic updates. Without a connection, the practical option is to hold separate stock for the site - a reserved quantity not sold in store. It is less efficient and far safer than shared stock updated by hand.
A customer bought online and wants to return in store. What now?
Follow a procedure defined in advance: how the transaction is identified, who refunds, which payment method the money returns to, and which document is issued. Without one the cashier improvises - and then there is a cash refund against a card transaction, a gap that surfaces at month end.
Do I need one system that does everything?
Not necessarily. You need it to be clear who is master in each area - documents, stock, customers - and to have one unified report. Plenty of businesses run two connected systems perfectly well, and break precisely when nobody decided who rules.
Keep reading
Related service
Inventory & Purchasing
SKU-level stock, reorder rules and an approval flow that leaves a record.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.