E-invoicing for micro household businesses: what works for a banh mi cart or a street noodle vendor?

As of January 1, 2026, under Resolution 68-NQ/TW on private-sector economic development, the flat-rate presumptive tax regime (thuế khoán) has been formally abolished for household businesses nationwide — every household business must now self-declare tax based on actual revenue instead of a fixed amount pre-set by the tax authority. In parallel, Decree 70/2025/NĐ-CP (amending Decree 123/2020/NĐ-CP) requires household businesses with annual revenue of 1 billion VND or more to issue e-invoices generated from a cash register connected directly to the tax authority's data system. This is no longer a concern only for restaurant chains or large taxi fleets — a popular banh mi cart, a street noodle stall, or a well-known mango-shake cart parked at a fixed spot can also cross that revenue threshold. And even for those who don't, abolishing presumptive tax still forces every vendor to track actual daily revenue somehow — rather than simply estimating it.

Why the taxi or restaurant solution doesn't transfer to street vendors

We previously wrote about a real-time e-invoicing architecture for taxi fleets — the core problem there was that a mechanical taximeter can't talk to an IT system. For street vendors, the underlying constraints are entirely different: there's no fixed checkout counter, no stable power source to plug in a POS terminal, and — most importantly — the vendor typically works alone, cooking, selling, and making change at the same time, with no dedicated staff to operate hardware or handle paperwork. A solution designed around a restaurant's fixed counter and dedicated cashier fails at the very first step when applied to a street noodle cart.

Three real-world constraints

**First: hardware budget is close to zero.** Profit from a single shift of street vending might be only a few hundred thousand VND. Requiring an investment in a dedicated 5–10 million VND POS terminal plus a receipt printer isn't realistic — equipment cost needs to be counted in the hundreds of thousands of VND, not millions, and ideally reuses a device the vendor already owns.

**Second: no fixed counter, and unreliable connectivity.** A banh mi cart might sell at one street corner in the morning and move to a different spot in the afternoon. There's no fixed wifi — every connection depends on the vendor's personal 4G data, and signal strength varies by area and time of day.

**Third: operational and time constraints.** A typical street-vending transaction lasts 15–30 seconds — the customer orders, the vendor cooks while calculating the price, makes change, the customer leaves. There's no time to open an app, navigate multiple screens, or enter complex data. Most vendors also aren't tech-savvy and have no time to learn a multi-step system.

Proposed architecture: minimal hardware, offline-first, one-tap

Hardware: the Android phone already on hand, printer optional

The solution requires no dedicated hardware — a mid-range Android phone (even a used one) is enough to run the order-recording app. The invoice is presented as a QR code shown directly on the vendor's phone screen: the customer scans it with Zalo or their phone camera to receive the e-invoice (PDF/XML) via Zalo or SMS — no paper printing required. A handheld mini Bluetooth printer (under 500,000 VND) is only an optional add-on for vendors who want to hand customers a paper receipt.

A one-tap app: preset items, usual prices

The interface has a single main screen showing the stall's common items/prices as large buttons (bánh mì thịt 25k, bánh mì trứng 20k...) — the vendor taps once or twice to create an order, no typing, no searching. For stalls with a changing menu or custom pricing (extra topping, a regular's discount), a simple "customize" button allows a quick adjustment without leaving the main screen.

Offline-first: selling doesn't wait for signal

This is the most important architectural principle, inherited from how we handled the analogous problem for taxis: each order is recorded locally on the phone immediately, using `order_id` as the idempotency key — with no wait for server confirmation. Once connectivity returns, a sync queue pushes the accumulated orders to the digital signing system and forwards them to the tax authority via the registered e-invoice provider's API (the same Invoice Builder → Digital Signing → submit-to-tax-authority flow described in the taxi post). The vendor is never blocked from selling just because of a momentary signal drop.

Automatic revenue-threshold tracking

Because e-invoicing and declaration obligations differ by revenue tier, the app automatically accumulates daily and monthly revenue and shows a simple indicator (e.g. a progress bar) of where the stall stands relative to the key thresholds. When approaching a threshold that changes its obligations, the app prompts the owner to contact an accountant or the tax authority — instead of leaving the owner to navigate complex tax rules alone, the software carries that tracking burden.

This is a perfect fit for a Module Sprint, not a full Pilot Build

An e-invoicing system for small household businesses is a clear, narrow-scope module — it doesn't require a multi-layer closed loop like the 6–8 week Pilot Builds we typically deliver. This is exactly the kind of problem suited to the Module Sprint tier we recently introduced: 3–4 weeks, 1–2 senior engineers, one production-ready module — enough for a chain of household businesses (multiple banh mi carts under one owner, a franchised noodle-stall chain) to roll out quickly without paying for a large enterprise system.

Conclusion

Abolishing presumptive tax pulls millions of small household businesses — including street vendors who never thought about the concept of an "e-invoice" — into a new compliance requirement. The right solution isn't a scaled-down restaurant POS system; it's a design built from scratch around the actual constraints: cheap hardware, no fixed counter, one-tap operation, and never blocking a sale over a dropped signal. Learn about KonexForge's Development capability, or get in touch if your stall or household-business chain needs a compliance solution that fits a real budget.