Running a multi-location restaurant or hospitality estate on Oracle Simphony point-of-sale, alongside NetSuite as the finance and inventory system of record, creates a specific integration problem: how do you move Guest Check data into clean financial transactions, at scale, across dozens of locations, without a single unmapped menu item or a missing Bill of Materials stopping revenue from posting? Threadgold built that integration for a multi-location hospitality group, and this is what changed once it went live.
The Challenge: Running NetSuite Across a Multi-Location POS Estate
The client is a major hospitality and retail group in Malta, operating more than 50 outlets and 300+ POS terminals across multiple brands, all running on Oracle Simphony. Every one of those terminals generates Guest Check data throughout the day: food and beverage sales, tax treatment, payment methods, menu items sold against recipes and Bills of Materials. Getting that data into NetSuite cleanly, every day, across every location, without someone manually re-keying figures or reconciling POS totals against the general ledger by hand, is the engineering problem behind any NetSuite and Simphony integration.
Three things made this harder than a single-site POS integration. First, Simphony's menu items are not guaranteed to have a matching item configured in NetSuite at any given moment, and a naive integration would let one missing match block an entire day's Cash Sale creation. Second, many of the items sold are Assembly Items built from recipes, and Simphony's own recipe structure does not map directly onto NetSuite's Bill of Materials and BOM Revision model, so inventory depletion had to be handled as a genuinely separate process from revenue posting, not bundled into the same transaction. Third, NetSuite enforces a hard limit of five concurrent scripts per account, and a hospitality group running Simphony across 50-plus outlets cannot simply fire every location's integration at once without hitting that ceiling.
None of this is unique to one client. Any hospitality group evaluating NetSuite for restaurants or comparing NetSuite against other options for NetSuite multi-location POS management will hit some version of these three problems.
The Solution: Connecting Oracle Simphony to NetSuite
Threadgold built a NetSuite Simphony connector around a simple rule: nothing should ever be allowed to block a day's revenue from posting. It works in three stages:
- Technical Foundations - authentication, menu mapping and integration logging, so every run has a clean record of what happened.
- Guest Checks to Cash Sales - a daily, per-location automated posting run, so revenue lands in NetSuite without manual re-keying.
- Item Depletion Suitelet - controlled inventory and BOM consumption, triggered separately from revenue posting so a missing recipe configuration can never hold up a day's sales.
Two problems needed solving beyond the basic data transfer. First, Simphony menu items don't always have a matching item configured in NetSuite, and letting one missing match block an entire day's Cash Sales wasn't an option. The Unmatched Item Logic catches this instead: an unrecognised item still posts under a generic placeholder, with the original Simphony details preserved for later clean-up. If a Simphony item called Margherita Pizza doesn't yet exist as a NetSuite item, for instance, the Cash Sale still records correctly with the original item name kept on file, rather than the whole transaction stalling.
Second, restaurant recipes aren't one level deep, and Simphony's own recipe structure doesn't map cleanly onto NetSuite's Bill of Materials. A pizza might depend on a pizza sauce, which itself depends on a marinara base three levels down, and the connector works through that entire chain automatically, generating every Work Order and Assembly Build along the way, rather than stopping at the first level.
The Business Impact
The engineering behind this only matters because of what it changed. For a major hospitality and retail group in Malta operating more than 50 outlets and 300+ POS terminals across multiple brands, the results showed up in finance and operations:
- Manual stock checks down from four a month to one. Previously the single most time-consuming manual task in the old process.
- Real-time profit and loss reporting, not monthly. Finance now works from a current picture instead of a month-old one.
- Reduced purchasing wastage. Automated order processing eliminated the duplicate orders that had previously driven unnecessary purchasing and food waste.
- Automatic reconciliation. Transactions post to NetSuite automatically, removing the manual matching that used to sit between POS and the general ledger.
- Predictable card processing fees. Each transaction is automatically assigned the correct payment method, so fees can be forecast rather than estimated after the fact.
- Less headcount time on manual verification. Staff spend less time verifying stock levels, uploading transactions and checking for errors.
None of these are one-off gains from a single clean-up exercise. They're structural changes that hold as the estate grows, because the underlying integration is designed to scale location by location rather than needing rework every time a new outlet opens.
Conclusion
The pattern here holds for any hospitality group running Simphony at scale: the moment a POS-to-ERP integration is treated as a simple data pipe, one missing menu item or one unconfigured recipe becomes an entire day's revenue stuck in limbo. Building for failure at the item level and the recipe level, rather than assuming everything will always match cleanly, is what let Threadgold take this client from monthly stock checks and month-old profit and loss reporting to a real-time view without adding headcount.
For a hospitality group weighing up NetSuite implementation against the realities of a live, multi-brand POS estate, this kind of resilience is usually the difference between an integration that survives contact with a large multi-site rollout and one that doesn't.
If you're evaluating a similar project, our NetSuite pricing guide covers what an implementation and integration project like this one typically costs.
