Any register. Any outlet. Posted nightly.
We read whatever is on your counter — through its interface if it has one, or the printed reading if it does not. Nobody retypes a day of sales.
| Ayala — 4 tills | online | ₱284,120 | posted |
| IT Park — 3 tills | online | ₱241,880 | posted |
| Mactan — 2 tills | online | ₱198,340 | posted |
| Banilad — 2 tills | offline 14 min, replayed | ₱176,900 | posted |
| Talamban — 2 tills | online | ₱121,455 | posted |
| Duplicate rings | same key twice is a no-op | 0 | none |
Point of sale integration, shift and till control, open bills, gift certificates and advance orders, with one journal per site per day.
What it actually does.
The till you already have
Replacing a working register is a cost with no benefit. What changes is that the reading reaches the ledger without anybody keying it, and that the day cannot be quietly skipped.
- Any register — API, database, scheduled file, or the printed reading.
- A day that has not been posted says so; it never reads as zero sales.
- Tenders split so the settlement can be matched to the bank later.
The statutory discounts are separated because the BIR asks for them separately.
A shift that actually reconciles
Open with the float counted, declare at the end without seeing the expected figure, and the difference is recorded against the shift and the person — over or short.
- Declaring after seeing the expected figure is not a count; the screen withholds it.
- Open bills block a clean close, deliberately.
- Voids and discounts attributed, because the pattern is the finding.
Counted by a person, totalled from the receipts, and the difference named to a shift rather than to a day.
What you sold, and what it earned
Every item ranked by how well it sells against what it contributes, per site — because an item can be a star downtown and a dog in a mall, and averaging them hides both.
- Gift certificates as a tracked liability until redeemed or expired.
- Advance orders with deposits held as customer deposits, not revenue.
- Senior and PWD discounts captured with the ID at the counter.
The ones people ask about this.
Which POS systems do you support?
All of them, in the sense that matters: if it has an interface we use it, and if it does not, the printed reading is read. That is the fallback that makes the answer 'any'.
Do we have to change how the cashiers work?
No. The change is behind the counter, not at it.
What if a branch forgets to close the till?
The day shows as not posted rather than as zero sales, and it appears on the morning screen. A zero for a trading day is a lie the system will not tell.
Can we run our own POS on DBS One instead?
Yes — fast tills, offline-safe, every branch on one price list. Several clients do.
Nothing here is a separate product.
See it on your own figures.
Bring one ordinary day from your business and we will run it through in front of you, on your own items and your own prices.