Close the till.
The books are done.
Connect your POS and each day's sales land in Bukku on their own — one invoice per outlet per day, broken down by payment method and item, ready to reconcile. Straight from your POS, nothing in between.
Two direct connections. One route for everything else.
StoreHub connects through Flow, our sales-sync module. FeedMe built its own connection on the Bukku API. Every other POS can still land in your books daily, with a file.
Retail and F&B POS widely used across Malaysian shops and cafés. The first POS to connect to Bukku — orders sync every midnight into a daily digest.
FLOW Direct syncstorehub.com ↗F&B POS for restaurants and cafés — table ordering, QR menus, kitchen displays. FeedMe built the connection itself on the Bukku API: sales, payments and items post from FeedMe, one invoice per outlet per day.
API Direct syncfeedme.cc ↗Using something else? Export the day's sales report from your POS, fill Bukku's batch template and import it. A minute a day, on every plan.
XLSX Daily file uploadHow the daily file works ↓We add direct POS connections based on what our users run. Using a POS you'd like connected? Tell us which one.
Connect once. Wake up reconciled.
Two direct routes, one result: each day's sales in Bukku with every ringgit routed to the right account.
- Connect in Bukku
Control Panel › Flow Streams › Connect, enter the credentials StoreHub gives you, choose auto-sync, a start date, and sales by SKU or as one line. - Every night, one digestBukku pulls the day's orders and consolidates them per outlet — total, payment breakdown, items by SKU, every order underneath.
- Review, or let it postAuto-invoice and the digest becomes an invoice on its own. Or open it under Flow, check, then post.
- Connect in FeedMeAdd the Bukku integration in FeedMe, paste your Bukku API token and subdomain, pick the outlet.
- Map onceMatch FeedMe's items, taxes and payment methods to your Bukku account codes, and choose how sales group — say, one invoice a day with each payment as its own receipt.
- Sales post on their ownSales, payments and items flow into Bukku from FeedMe's side. Already e-invoicing through FeedMe? Mark it external so Bukku doesn't submit twice.
Built for how a shop actually runs
Nobody wants 300 receipts in their invoice list. Both routes give you one invoice per outlet per day, with the cash, card and e-wallet totals mapped to the accounts they really settle into — and the detail still there when you need to drill in.
- One invoice per outlet per day, not hundreds of receipts
- Cash to cash-on-hand, cards and e-wallets to the bank they settle into
- Items on the invoice deduct stock and post cost of goods sold
- Outlets stay separate, so you can read each branch on its own
No direct connection? One file a day.
Every POS can print a daily sales report. Put it into Bukku's batch template and the day's sales post as cash invoices — same books, same reports, no re-keying.
- Export the day's salesFrom your POS's end-of-day or Z report, by outlet.
- Fill the batch templateOne row per day, or one per receipt if you want the detail. Payment method, items and tax have their own columns.
- Import into Bukku
Sales › Invoices › ⋯ › Batch Cash Invoices › Import. Review the rows, save, done.
| Date | Outlet | Item | Qty | Payment | Amount |
|---|---|---|---|---|---|
| 24/09/2026 | Bangsar | Latte 12oz | 96 | Card | 1,248.00 |
| 24/09/2026 | Bangsar | Kaya toast set | 71 | Cash | 852.00 |
| 24/09/2026 | Bangsar | Cold brew 350ml | 58 | TnG eWallet | 812.00 |
| 24/09/2026 | Bangsar | Nasi lemak bungkus | 64 | DuitNow QR | 576.00 |
| 24/09/2026 | Bangsar | Other items | — | Mixed | 376.50 |
Anyone who counts the till at night
Cafés & restaurants
Hundreds of small tickets, five ways to pay. Your outlet's day becomes one invoice, with e-wallet and card totals ready to match against settlements.
Retail shops
Sales by SKU keep stock on hand and cost of goods sold right in Bukku without a separate stock count — margin by product, straight from the till.
Multi-outlet brands
Each branch connects as its own stream with its own digests and invoices, so you can read the business by outlet and as a whole.
What's included, and where
StoreHub via Flow — every plan, with a monthly order quota
Every POS order that syncs through Flow counts once, even though it's posted as part of a daily digest. Resets monthly.
FeedMe via API needs a plan with API access — Seed and above — and doesn't count against this quota. The daily file route has no quota and works on every plan. Full detail in the plan comparison →
Malaysia's SMEs run on Bukku — at scale
POS questions, answered
Tomorrow morning, yesterday's sales are in
Start your 30-day Elite trial, connect your POS, and see the first digest land overnight — no credit card required.