The BC-50 at your pass prints the kitchen ticket and, when you choose, the fiscal receipt for the same order. One receipt per order, built from what the guest actually paid — nobody re-types the order at the till.
The Datecs BlueCash-50 is an Android terminal, a fiscal printer and a payment pinpad in one box. The Ordering.Tools app runs on the device itself. Online orders from your website, QR menus, pickup and delivery come out of its printer as kitchen tickets — in Cyrillic, without a separate printer or a PC.
The same fiscal module can also register a real fiscal receipt for the order. Each device chooses what auto-print produces: the standard kitchen ticket, the fiscal receipt, or both. The receipt is built on the server from the order's lines and payments, issued once per order, and can be reversed with a storno from the order screen.
The receipt is built from the order itself — dishes, delivery fee, discount and payment type. Nobody copies an online order into the fiscal device by hand.
A fiscal receipt printed twice is a sale counted twice. The order carries one receipt record, so a second device or a second tap cannot issue another.
If the lines do not add up to the order total to the cent, the receipt is refused before anything is registered. The fiscal module never ends up with a half-finished document.
Kitchen tickets and fiscal receipts come out of the same BC-50. Each device decides which of the two it prints.
The BC-50 is a certified device: Datecs decides which apps may be installed and fiscalizes the module. Arrange both with them, then install the Ordering.Tools app and sign in.
In Settings → Printing, enter the operator, password and till number programmed in the module, the VAT group, and how each payment type is registered.
Pick standard ticket, fiscal receipt or both for this device. Choose whether orders print on arrival or when they are confirmed and go to the kitchen.
Place a small order, let the receipt print, then reverse it with a storno from the Orders Board. That walks the whole chain once before real service.
Every device with a fiscal printer chooses what comes out for a new order. A device whose module is not fiscalized is never offered the fiscal options.
Before printing, the device claims the order's single receipt record on the server. Two devices racing for the same order — only one wins.
The server builds the receipt from the order: dish lines, the delivery fee as a line, the order discount, and the payments. The module computes the total itself, so the two must match.
The order screen on the Orders Board has a Fiscal receipt button, with a confirmation first. Once issued, the same button becomes Storno.
The order comes in, the kitchen ticket and the fiscal receipt print one after the other, and the receipt goes in the bag with the courier.
The receipt registers the payment as card at handover — the type you mapped for it. Nobody keys the order into the till.
Open the order on the Orders Board and press Storno. The reversal cites the original receipt and carries the same lines.
The module refuses, the receipt is marked failed and waits in the queue. Change the roll and it prints — still only once.
One BC-50 prints kitchen tickets, the other prints receipts. Even if both try the same order, only one receipt is issued.
With print-on-confirm, nothing prints until someone accepts the order. The ticket comes out the moment it goes to the kitchen.
In Bulgaria, a sale paid in cash or by card at the venue is registered with a fiscal receipt from a fiscal device. For online orders that usually means someone re-typing the order into the till. On a Datecs BC-50 running Ordering.Tools, the receipt is built from the order itself and printed by the device's own fiscal module.
The BC-50 combines an Android terminal, a fiscal printer and a pinpad. Ordering.Tools runs on it like on any order station: new orders arrive on screen and the kitchen ticket prints — on arrival, or only when the order is confirmed. Printing a fiscal receipt is an extra, per-device choice.
Every line is computed in whole cents on the server. Dishes and paid extras become sale lines, the delivery fee is its own line, the order discount is a subtotal discount and a gift card is a payment. The device checks the module's subtotal against the expected total before any payment is registered.
Orders paid online by card can be registered with a fiscal receipt, or — for delivery orders — handled under the e-shop regime of Наредба Н-18 with a sales document and a monthly audit file. Which one fits is your decision with your accountant. The daily Z-report stays on the fiscal device, as before.
Yes, through the fiscal module of a Datecs BC-50 running the Ordering.Tools app. Each device chooses whether auto-print produces the kitchen ticket, the fiscal receipt or both, and any order can also get its receipt with a button on the Orders Board.
A BC-50 with a fiscalized module and the Ordering.Tools app installed — Datecs controls both, so arrange them with Datecs or your service technician. Then enter the operator, password, till number and VAT group in Settings → Printing.
No. Each order has one receipt record on the server, and a device must claim it before printing. A second device or a second tap is refused. If a print was started but never confirmed, an operator checks the paper before anything is reissued.
Press Storno on the order in the Orders Board. The storno reverses the receipt exactly as it was issued and cites its number. It is not automatic: a storno is a fiscal document, so the operator at the device decides.
Dishes and paid extras are sale lines, the delivery fee is a line, and an order discount is a subtotal discount. A gift card is registered as a payment, and the rest under the payment type you mapped. The tip is not on the receipt.
They can get one, under the payment type your accountant chooses. Delivery orders paid online by card can instead fall under the e-shop regime of Наредба Н-18. It is the venue's choice, so check it with your accountant before you set up auto-print.
Online orders, kitchen tickets and fiscal receipts on one device — one receipt per order, built from what the guest paid.
Other tools restaurants use alongside this one.
For delivery orders paid online by card, Ordering.Tools issues the numbered sales document and builds the monthly audit file (Приложение 38) that you upload to НАП. Opt-in per venue; off until you switch it on.
Learn moreEvery online order prints on your kitchen thermal printer the moment it arrives. Auto-print runs in the background. No tapping screens, no refreshing tabs. Paper does not crash.
Learn moreStripe, myPOS, BORICA, Viva.com, DSK Bank, Barsy POS, and cash. When one method fails, customers switch to another -- without losing their order.
Learn moreConnect your PBX to Ordering.Tools and operators see the caller's full history the moment the phone rings — placing the order in seconds.
Learn more