Skip to content
Guide
Sales Workflow Guides
Synced Sales: Who Watches Each Feed

Synced Sales: Decide Who Watches Each Feed, and Empty the Offline Tills

Steps 3 and 4 of Sales That Arrive From Another System: give every feed a person who watches it, and empty every offline till’s queue before the branch closes. It follows Step 2, where you worked out what each way posts and who presses FINAL; Step 5 then runs the check this page sets up.

The running example: GadgetSphere’s online store sends about 380 sales invoices a day through the integration API, the distribution company’s invoices sync from EMP, two marketplace shops arrive as sales orders, and the two Kota Kinabalu branches (GS-KK-01, GS-KK-02) run their tills in Offline Mode, because the mall connection drops in the afternoons.

Before anyone clears the browser on an offline till, reinstalls it or swaps the machine, empty its Transaction Queue with SYNC ALL: the queued bills live only in that browser.

  1. Step 3: decide who watches each feed, and when.
  2. Step 4: empty every offline till’s queue before the branch closes.

Step 3: Decide who watches each feed, and when

The outcome: every feed has a named person, a time of day and a test they can pass or fail.

BigLedger keeps no list of the feeds you expect, so it cannot notice when one goes quiet. Someone in your business has to hold that list. Write it down once:

FeedWho watches itWhenThey know it is fine when…
Online store to BigLedgerThe accounts person for GSOEvery working morning, before 10:00yesterday’s count and total in BigLedger equal the store’s own day-end report
EMP to BigLedgerThe accounts person for GSDEvery working morningyesterday’s count equals EMP’s. If your business has the EMP missing-document e-mail, it arrived today (Step 5)
Marketplace shopsThe e-commerce teamEvery morning, and after any change to the shopyesterday’s marketplace orders are on the marketplace branch, and the branch’s connection record was updated today (EcomSync troubleshooting)
Offline tillsThe branch supervisorAt close, every daythe till’s Transaction Queue is empty (Step 4)
File importsWhoever imports the fileStraight after each importthe import shows no failed rows, and the count matches the file

Keep the person who reconciles a feed separate from the person who fixes it. If the person who runs the integration also signs off its daily count, a feed that is quietly dropping one branch’s sales can go unnoticed for weeks.

Step 4: Empty every offline till’s queue before the branch closes

The outcome: every sale rung up today is in BigLedger tonight, not sitting on a till.

POS General › (the till) › Transaction Queue

With Offline Mode on, the till keeps working when the connection drops. It holds each finished bill in a Transaction Queue on that till: in that browser, on that machine. The queue is sent to BigLedger only when:

  • somebody opens the Transaction Queue tab and at least 15 minutes have passed since the last send, or
  • somebody presses SYNC ALL.

Reconnecting does not send the queue by itself, and nothing sends it on a timer. A till that was offline at 15:00 and back online by 15:20 still has the afternoon’s bills on it at closing time. Nobody opened the tab, so nothing was sent.

At close, the supervisor opens the tab on every offline till, presses SYNC ALL, and waits until the queue is empty.

If you skip this: the bills exist only on that till. The branch’s takings and the stock look wrong in BigLedger until somebody opens the tab. If the browser data on the till is cleared, or the till is swapped, before the queue is empty, those bills are gone from BigLedger’s reach and have to be re-created from the paper receipts.

What success looks like for this part

Every feed on your list has a named person, a time of day and a test they can pass or fail, and the person who signs off a feed’s daily count is not the person who runs or fixes it. At close, every offline till’s Transaction Queue is empty: the supervisor opened the tab and saw it, and did not just assume it.

Common mistakes in this part

Letting the integration’s owner sign off its own count. The person who fixes a feed is the person least likely to notice that it drops one branch. Give the daily count to somebody else.

Clearing the browser on an offline till. The Transaction Queue lives in that browser. Empty it with SYNC ALL before anyone clears the cache, reinstalls or swaps the machine.

The rest are on the guide’s first page and on The Morning Check.

Related documentation

Last updated on
Sales That Arrive From Another System — and How to Notice When They StopSynced Sales: The Morning Check