One order state machine
Every channel maps onto it at the boundary, so four external vocabularies never reach your database.
The operator's systems, not the diner's app. One order moving through dine-in, takeaway, drive-through and three aggregators, and everything that has to stay true at every hop: menu and availability, kitchen routing, card scope, and the franchise numbers that reconcile at the end of the week.
Tell us what you are building
Food service software development builds the operator's systems: one order model that dine-in, takeaway, drive-through and the delivery aggregators all map onto, kitchen routing above it, and reporting that reconciles at the end of the week. Your point of sale owns money and your kitchen display owns time. Neither can answer the other's question.
Our work
No restaurant, franchise or cloud kitchen is among our clients, and saying so now is cheaper than you finding out on the second call. What we have shipped is the two halves a food service platform is made of: ordering and fulfilment with a back of house app behind it, and an ingestion layer that normalises what more than 25 external platforms send.
Scope
Eight pieces of work. Most engagements are three or four, and what your till can emit decides what the rest take.
Every channel maps onto it at the boundary, so four external vocabularies never reach your database.
One definition of what you sell, publishing outward to the till and every channel, instead of four portals and a PDF.
Faster than a menu publish and with its own permissions, so a sold out item stops selling during service.
Every channel behind a queue, every handler idempotent on their order id, because duplicates and out of order delivery are certain.
What every site must emit, in what shape and by when, so royalty comes from observed transactions.
Stock modelled against the physical kitchen with brands as catalogues above it, so one brand's sale depletes the shelf for all.
Integration
An integration project with a state machine at the centre of it. These are the systems a build has to meet; the work we have shipped is on the two case study pages above.
| System | Record for | The constraint that decides the plan |
|---|---|---|
| Point of sale software | Money. Every transaction, tender and refund, and the figure the bank statement has to agree with. | Toast, Square, Lightspeed, Revel, Oracle MICROS and Petpooja all turn up here, and the interface decides the plan rather than the brand: a documented REST API, a webhook feed, or a nightly file drop. Establish which in week one. |
| Kitchen display and production | Time. When a ticket was fired, bumped and completed, which almost never reaches head office. | Whether it can emit those events with timestamps. A screen that only draws tickets leaves no record to report on. |
| Aggregator channels | Nothing you can rely on. Each has its own menu model, order shape and retry behaviour. | Uber Eats, DoorDash, Deliveroo, Just Eat, Swiggy, Zomato and Talabat are the channels a build meets. Treat each as untrusted input behind a queue, with the mapping in its own adapter. |
| Payment provider | The card transaction, and the tokenisation boundary that decides how much of your estate is in scope. | Whether card data ever reaches your own systems. A validated PCI listed P2PE solution takes the rest of the estate out of the cardholder data environment. |
The till is the record for money and the kitchen display is the record for time, and neither can answer the other's question. Settling that in week one makes reporting possible in month six. If what you want is the diner facing ordering app, start instead with our restaurant app development page.
Card and tax
One row changes how much of your estate an assessor looks at and two change your launch date. Every row names its instrument and its date.
| Instrument | What it forces the software to do | When |
|---|---|---|
| PCI DSS v4.0.1 | Requirement 6.4.3 wants every script loading in the payer's browser authorised, integrity assured and inventoried with a written justification. Requirement 11.6.1 wants tamper detection on the payment page's headers and content as the browser receives them, checked at least every seven days or on a frequency set by a targeted risk analysis under 12.3.1. | PCI SSC published v4.0.1 on 11 June 2024 and retired v4.0 on 31 December 2024. Its future dated requirements became mandatory on 31 March 2025. |
| Which questionnaire you land in, and what P2PE does to scope | SAQ B-IP is for standalone PCI listed approved PTS terminals linked to the processor and nothing else, storing no account data. SAQ C is for a till application on the internet, single store network, no stored account data. Neither covers e-commerce, so web ordering moves you off both. SAQ P2PE carries only Requirement 3, Requirement 9 and the policy requirements, provided the solution is on PCI SSC's validated list and unexpired and no system holds clear text account data. | October 2024 editions for v4.0.1 |
| India, GST e-invoicing and the IRN | Report every covered document to an Invoice Registration Portal and carry the IRN back: CGST rule 48(5) says an invoice issued any other way by a covered person is not an invoice. Scope is supplies to registered persons, SEZs, exports and deemed exports, and the official FAQ states that reporting B2C invoices by notified persons is not applicable or allowed at present. The franchise exposure is franchisor to franchisee invoicing. | Notification No. 10/2023 Central Tax, in force since 1 August 2023, where aggregate turnover exceeded Rs 5 crore in any year from 2017-18 onwards |
| India, the 30 day reporting window | At turnover of Rs 10 crore and above, every invoice, credit note and debit note that gets an IRN has to reach the portal within 30 days of the document date, and the portal refuses a later attempt, so billing software queues, retries and alarms inside the window. The official e-invoice feed still carries an earlier advisory dated 13 August 2024 putting the limit at Rs 100 crore and above, superseded by the November 2024 one. | The GSTN advisory of 5 November 2024, applying since 1 April 2025 |
| Oman, VAT and Fawtara e-invoicing | VAT is 5 percent of the taxable value under Royal Decree No. 121/2020 Article 36, which commences 180 days after gazette publication rather than on a stated date. Fawtara wants every tax invoice in an approved, secured electronic format with a unique number, simplified tax invoices included, so the obligation reaches counter sales. Paper, PDF and emailed images do not qualify, and the phase is self assessed on total annual supplies at VAT group level. | Tax Authority Decision No. 189/2026, issued 3 August 2026, amends the VAT Executive Regulations and sets 1 April 2027 and 1 October 2027. The Authority's FAQ makes the earlier date apply if either your supplies from April 2026 to 31 March 2027 exceed OMR 5,000,000 or the supplies you expect from 1 April 2027 to 31 March 2028 exceed it, so a forecast above the threshold moves you six months earlier. Nothing is mandatory in 2026. |
Keep the regulated concern in its own layer rather than threading it through the order path. ISO 27001 comes from a certification body, SOC 2 is an AICPA attestation examination by a CPA firm, and PCI compliance is assessed by a qualified assessor. For the same till estate with a different basket, see retail and commerce software development.
Food safety
Traceability, allergens and menu labelling are three data model requirements wearing one word. Each row names the section that sets it.
| Instrument | What it forces the software to do | When |
|---|---|---|
| FDA Food Traceability Rule, 21 CFR Part 1 Subpart S | For a restaurant the operative event is Receiving under 21 CFR 1.1345: per lot, the traceability lot code, quantity and unit, product description, the immediate previous source location, where it was received, the date, the lot code source, and the reference document type and number. Records reach FDA within 24 hours of a request under 1.1455(c)(1), and during an outbreak in an electronic sortable spreadsheet under 1.1455(c)(3)(ii). Retention is two years. | Published 21 November 2022 at 87 FR 70910 |
| Which foods, and which restaurants are exempt | The Food Traceability List at 21 CFR 1.1300 runs to fresh leafy greens, fresh-cut fruit and vegetables, tomatoes, melons, herbs, sprouts, shell eggs, nut butters, soft cheeses, finfish, crustaceans, molluscan shellfish and ready-to-eat deli salads, and reaches a listed food used as an ingredient while it keeps that form. 21 CFR 1.1305(i) exempts a restaurant whose average annual food sales over the previous three years are no more than US$250,000, and 1.1455(c)(3)(iii)(B) lets one at no more than US$1 million answer in a form other than a sortable spreadsheet. | Current list. Additions take effect two years after a final notice, deletions immediately |
| When the rule bites, stated honestly | Public Law 119-37 section 780, approved 12 November 2025, bars FDA from using funds appropriated by that Act to administer or enforce the rule before 20 July 2028. FDA has proposed, not finalised, moving the compliance date there, at 90 FR 38084 dated 7 August 2025, and FDA's own rule page still carries the date the rule set, 20 January 2026. Draft guidance at 91 FR 64629, published 9 October 2026, offers enforcement discretion between those two sales figures and states that it is not binding. | Not enforceable before 20 July 2028, on the appropriations bar rather than a finalised rule |
| FALCPA allergens on the menu item record | Carry the nine major food allergens as structured data on every ingredient, sub recipe and menu item, able to roll up to a finished plate, because the declaration has to name the food source. FDA names them as milk, eggs, fish, Crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame. The carve-out decides the data model: FALCPA labelling reaches an establishment that packages, labels and offers products, and not food placed in a wrapper or container after a customer's order at the point of purchase. The pre packaged line is covered and the made to order plate is not, while allergen filters and staff answers still need the fields. | Labelling applies to food labelled on or after 1 January 2006, with sesame as the ninth major allergen since 1 January 2023 |
| Menu calorie labelling, 21 CFR 101.11 | A covered establishment is one in a chain of 20 or more locations under the same name offering substantially the same menu items. Calories go next to the name or price, in type no smaller, rounded to the nearest 5 up to 50 calories and the nearest 10 above. On request eleven nutrient fields have to be available, from total calories to protein, so a calorie only model is not enough. | In force in the current Code of Federal Regulations |
The system side is the same under all of these: batch and supplier traceability from goods in through prep, temperature and time captured rather than transcribed, allergen data on the menu item, and an export your auditor can sort. For the kitchen inside a hotel, see travel and hospitality software development.
Transparency
We publish the hours and the module breakdown, and a fixed price follows discovery. Module by module, with the drivers ranked, so you can argue with any line before anyone quotes.
Worked example
700 hours
Six modules added up below, each inside its own range.
Typical timeline
10 to 16 weeks
The slow part is agreeing one menu definition across four channels.
Useful hours
510 to 980
Every module at its minimum, through to every maximum.
| Driver | Hours |
|---|---|
| What your till can actually emitA documented API and a nightly CSV are the same requirement and a different project. Establish it in week one. | Highest impact |
| How many channels you runThe second aggregator is expensive because it forces the abstraction. The fourth is cheap because the abstraction exists. | High |
| Whether a menu source of truth existsIn most operations it does not, and building one means reconciling four channel catalogues that have quietly diverged. | High |
| Single operator or franchise networkA network adds the reporting contract, per site permissions and royalty computation. A single operator needs none of it. | Medium |
| Number of fiscal jurisdictionsThe first is a build and each one after it is an adapter, provided the fiscal layer stayed out of the order path. | Medium |
| Module | Hours |
|---|---|
| Menu and availability model | 70 to 140 |
| Till and payment integration | 110 to 200 |
| Kitchen display and routing | 90 to 170 |
| Aggregator channel integration | 100 to 190 |
| Franchise reporting and reconciliation | 80 to 160 |
| Fiscal and compliance output | 60 to 120 |
Delivery
Five phases, each named by the artifact it hands you, so you can ask to see one.
Phase 01
What every system can emit and accept, in writing, from calling the APIs rather than reading the brochure.
Phase 02
One state machine every channel maps onto, agreed on paper first. Channel vocabularies stop at the boundary.
Phase 03
One source of truth for what you sell, publishing outward, with availability on a faster path.
Phase 04
Routing, display and completion, with time data kept as a record rather than discarded at the end of service.
Phase 05
Money from the till joined to time from the kitchen on one order id, fiscal output behind its own adapter.
It depends on where card data goes. Standalone PCI listed approved PTS terminals linked to the processor and nothing else point at SAQ B-IP. A till application on the internet, single store network, no stored account data, points at SAQ C. A validated, unexpired PCI listed P2PE solution points at SAQ P2PE, which carries only Requirement 3, Requirement 9 and the policy requirements. Neither B-IP nor C survives web ordering.
Two money tests in the rule decide it. 21 CFR 1.1305(i) exempts a restaurant whose average annual food sales over the previous three years are no more than US$250,000, and 1.1455(c)(3)(iii)(B) lets one at no more than US$1 million answer in a form other than an electronic sortable spreadsheet. Public Law 119-37 section 780, approved 12 November 2025, bars enforcement spending before 20 July 2028.
No. The obligation runs to supplies to registered persons, SEZs, exports and deemed exports, and the official GST e-invoice FAQ states that reporting B2C invoices by notified persons is not applicable or allowed at present, so the till branches on whether the buyer gave a GSTIN. At Rs 10 crore and above, the GSTN advisory of 5 November 2024 has required reporting within 30 days of the document date since 1 April 2025.
Tax Authority Decision No. 189/2026, issued 3 August 2026, sets 1 April 2027 and 1 October 2027. Per the Authority's FAQ the earlier date applies if either your supplies from April 2026 to 31 March 2027 exceed OMR 5,000,000 or the supplies you expect from 1 April 2027 to 31 March 2028 exceed it. The count includes taxable supplies other than capital assets, goods and services under the reverse charge, and intra-GCC supplies, and for a VAT group it is assessed at group level rather than per member. Nothing is mandatory in 2026, and voluntary adoption is allowed before your date.
One internal definition, published outward, with every channel's vocabulary mapped at the boundary. Modifier groups, combos and portion sizes are where the four models diverge, so those get agreed on paper before anything is built against them. Availability runs on its own faster path, because a sold out item cannot wait for a menu publish.
We build the systems and the records that let you satisfy them, and the certificate comes from elsewhere: ISO 27001 from a certification body, SOC 2 as an AICPA attestation examination by a CPA firm, PCI compliance from a qualified assessor. On the food side that means lot coded receiving records carrying the Key Data Elements 21 CFR 1.1345 lists, a sortable export, and the nine FALCPA allergens as fields on every ingredient and sub recipe.
The brand matters less than the interface. Toast, Square, Lightspeed, Revel, Oracle MICROS and Petpooja all turn up in this sector, and each exposes something different: a documented REST API, a webhook feed, or a nightly file drop. We read your till's capability first, by calling it where we can, and that answer decides whether the project is an integration or a rebuild.
Three steps with a shape attached to each.
Bring the name of your till, your channel list, and one week of numbers that did not reconcile.
We read what your till can actually emit, from its API documentation and where possible by calling it.
The modules, the hour ranges and the arithmetic. If middleware covers you, it says that instead, and it is yours either way.
Almost every question on this page resolves to that one. We will read your till's capability and tell you whether this is an integration or a rebuild, with the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
The till side of the work
Order state and reconciliation
Head office reporting
Exception and reconciliation queues
Supplier invoices and lot records
The diner facing ordering app
Same till estate, different basket
The kitchen inside a hotel
Every sector we build for
Guides on point of sale, kitchen and multi-channel order systems, written by the team that builds them.