Melba integrations: POS, suppliers,accounting 2026
More than 50 native connectors to point of sale systems (Lightspeed, Tiller, Hublow, Cashpad), wholesalers (Transgourmet, Davigel, Metro, Pomona) and accounting tools (Quadratus, Cegid, Sage, Pennylane), plus a public REST API to wire up anything that is not yet on the list.
This page lays out the full integration map, the data sync workflow between POS, stock, suppliers and accounting, the transparent status (native, beta or via API) of every connector and the procedure to request a new integration with a five-business-day SLA.
Melba integrations: POS, suppliers, accounting 2026
Picking a kitchen management platform is rarely a greenfield project: your restaurant is already running a POS, a wholesaler, an accounting firm and very often a workforce or reservations tool. The single question every tech buyer asks before signing is simple: will this new ERP plug cleanly into the existing stack, or will it force a painful migration of every other tool? Melba made the opposite call from most operators on the market: we integrate with your ecosystem, not the reverse. This page lists every available connector, the technical status of each, and the end-to-end data sync workflow that flows between the building blocks.
You will find here the map of the five integration families (POS, suppliers, accounting, BI and HR / scheduling), the detailed list of supported tools per category with the integration level (native, beta or via API), the technical architecture of data synchronisation, the public API documentation for custom needs, and the procedure to add a new tool to the roadmap. Three quantified case studies - multi-site chain on Lightspeed and Cegid, premium event caterer on Choco and Pennylane, public-catering central kitchen on EDIFACT and Quadratus - show the concrete value of an integrated stack.
40-word answer: how Melba connects to your stack
Melba ships 50+ native connectors (POS, wholesalers, accounting, BI, HR) plus a public REST API in JSON-API and OpenAPI v3 with OAuth2 and webhooks. Native connectors activate within hours, the public API is supported deployment. Five-business-day SLA on every new integration request.
Five integration families around the Melba core
The Melba ecosystem is organised as a hub-and-spoke around the central kitchen management engine. Five families of third-party tools plug in based on the data they exchange: incoming sales feed from POS, outgoing orders and incoming invoices for suppliers, accounting journal exports, external dataware for BI, and headcount sync with payroll for the food cost / labor cost pairing.
This star architecture means no third-party tool is a single point of failure: every category can be activated independently, every connector has a fallback (manual or API), and a vendor going dark never invalidates the historical data already consolidated in Melba. That decoupling is what lets you swap POS in mid-contract without losing traceability or having to re-parameterise recipes.
12 POS systems natively integrated with Melba
The POS feed is the most critical: it is the trigger for theoretical stock deduction, real food cost calculation and theoretical-vs-actual sales reconciliation. Melba supports the twelve leading POS systems on the French and European market, with an explicit integration level for each: native (transparent, automatic push), beta (in hardening, manual validation) or via API (configured by the customer or by a partner systems integrator).
Sync frequency is configurable per restaurant: real-time for high-turnover concepts where losing an hour matters (dark kitchens, delivery), hourly for classic commercial foodservice, or daily for public catering or environments where traceability outweighs speed.
15 wholesalers and marketplaces wired into the Melba catalogue
The supplier feed is bidirectional: outgoing orders (placed in the Melba interface or auto-triggered by stock threshold) and incoming invoices (received via EDI, API or OCR scan, then matched to the delivery note). Fifteen wholesalers and platforms are natively integrated, from generalist wholesalers (Transgourmet, Metro, Pro a Pro) to regional specialists (Pomona Group with TerreAzur, EpiSaveurs, PassionFroid) and multi-supplier marketplaces (Choco, Rekki, BlueCart). EDIFACT D96A is the standard for volumes above 500K EUR / year.
8 accounting and financial ERP systems connected
The accounting export closes the loop: every recorded purchase, every consolidated sale and every stock operation generates a journal entry that must land in the firm's or finance director's software. Melba supports eight French and European accounting targets in FEC format (the French regulatory standard for journal entries), customisable CSV and OFX for bank reconciliations. Account mapping (for example: account 607 Goods Purchased depending on ingredient nature) is configured once and stays stable month after month, avoiding year-end cleanup work.
External reporting, scheduling and reservations connected
Beyond the POS / suppliers / accounting triplet, Melba integrates with the cross-functional tools that drive operational experience: business intelligence for groups consolidating multiple sources, HR and scheduling to track the food cost / labor cost pairing, reservations to forecast production volumes, and delivery platforms for hybrid concepts. Most of these integrations run through the public REST API with OAuth2 authentication and webhooks for real-time event propagation.
End-to-end data synchronisation architecture
The data sync workflow shows how a real sale flows, from the ticket entered on the POS to the accounting entry, through stock deduction and automatic supplier ordering. This chain is what competitors advertise but rarely document: transparency on frequencies, latencies and reconciliation rules is what lets a tech buyer judge integration quality before signing.
Connect Melba to everything else: public REST API
For everything not on the native connector list, Melba exposes a public REST API in JSON-API format, documented in OpenAPI v3, with OAuth2 authentication, rate limiting and a dedicated sandbox environment. This technical autonomy is what lets restaurant groups with internal IT or a partner integrator cover non-standard cases in days rather than months of waiting on the vendor roadmap.
Get your tool added to the Melba roadmap
If the tool you use is neither in the native connectors nor covered by the public API, submit an integration request. The embedded form (HubSpot or Brevo depending on the channel) collects the necessary information: tool name, category, number of sites concerned, urgency level. The request is reviewed within five business days at most, with a qualified response: native connector to scope, addition to the public roadmap, integration via documented API, or routing to a partner integrator.
Case studies: 3 real Melba integrated stacks
Case 1 - Eight-restaurant commercial chain, 18M EUR revenue. Stack before Melba: Lightspeed Resto as POS, Transgourmet and Metro as wholesalers, Cegid Loop for accounting, Combo for scheduling, and a shared Excel file for recipes and food cost. The pain: three days of accounting entry per month, food cost calculated two weeks late, no visibility on theoretical-vs-actual sales gaps. Stack after Melba: native Lightspeed connector (real-time ticket-by-ticket sync), native Transgourmet and Metro connectors over EDIFACT, monthly FEC export to Cegid Loop, daily API sync with Combo. Six-month results: 2.4 food cost points recovered, two days of accounting entry saved every month, automatic alerting on gaps above 1 point.
Case 2 - Premium event caterer, 4.5M EUR revenue, mobile teams across 200 events / year. Stack: light mobile POS via Square for Restaurants (API integration), supplier orders via the Choco marketplace (native connector), Pennylane accounting (bi-monthly FEC export), event reservations via Sevenrooms. The specific need was to auto-trigger supplier orders as soon as an event menu was locked, respecting each wholesaler's lead time. Solution: Melba webhook on event-menu creation, Zapier integration to Choco for consolidated order push, Slack alerting for manual validation above 5 000 EUR. Outcome: 1.5 FTE saved on event procurement coordination, wholesaler service rate up from 91% to 97%.
Case 3 - Public-catering central kitchen, 8 000 meals / day, 36-month framework contract. Strong regulatory constraints: full allergen traceability, reliable audit trail, 10-year raw-flow retention. Stack: no POS (forecast-driven production), supplier orders in EDIFACT D96A to Pomona Group and Pro a Pro, Quadratus accounting with cost-centre-split mapping (school, retirement home, hospital), Power BI reporting on Melba dataset. See the central kitchen software context for the public-catering specifics. Outcome: 2025 regulatory audit cleared in two days instead of two weeks, zero traceability non-conformity, raw-material price drift held at 0.4 point thanks to real-time EDI.
FAQ - Melba integrations
Eight frequent questions raised by tech buyers (CIOs, COOs, software-selection project leads) at final evaluation, before signing. Answers below are calibrated for single-site, multi-site and public-catering contexts.
How does Melba connect to my POS?
For the twelve natively integrated POS systems, activation happens from the Melba admin UI by entering the POS API key (provided by your POS integrator). For unlisted POS systems, the public API lets you push or pull sales via webhook or hourly poll, with starter code samples in the OpenAPI v3 documentation.
What is the sync frequency between POS and Melba?
Configurable per restaurant between real-time (ticket-by-ticket), hourly or daily. The commercial-foodservice standard is hourly, the public-catering standard is daily, the dark-kitchen / delivery standard is real-time so intra-day food cost stays fresh.
Are supplier orders sent automatically?
Yes, if you enable the stock-threshold trigger. The rule is per-product configurable: automatic order when theoretical stock drops below a minimum, with a preferred supplier and a backup supplier if the first one is unavailable or out of delivery window.
Does Melba export accounting entries in FEC format?
Yes, monthly FEC by default, compliant with the January 2014 French decree on reliable audit trail. Customisable CSV and OFX export for bank reconciliation are also available. Account mapping is configured once per site and stays stable month after month.
Is there an extra cost per integration?
Native connectors are included in the Melba subscription, no extra fee. The public API is also included in the standard plan with a generous rate limit. Beyond the standard rate limit, an extended-rate-limit add-on is billed for very high-volume API groups.
What if my tool is not on the list?
Submit an integration request via the dedicated form. Qualified-response SLA is five business days. Three possible answers: native connector to scope (added to the roadmap), integration via documented API (you or a partner integrator implement it), or routing to a partner integrator if the effort is significant.
Is the Melba API publicly documented?
Yes, public OpenAPI v3 documentation, JSON-API format, OAuth2 authentication, dedicated sandbox for development and testing. The how-to-access-melba-api and using-melba-api blog posts walk developers through the ecosystem step by step.
How long does it take to activate a native connector?
From a few hours to two days depending on initial parameterisation complexity: Melba product <-> POS article mapping (two to six hours per POS), account mapping for accounting (two to four hours per site), supplier catalogue mapping (auto for EDI, manual for suppliers without structured feeds). No integration takes months.