Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v19.0
License
LGPL-3
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
2701 lines (Python / XML / JS)
Overview & Description
Aura Odoo TechSupports:Odoo 20Community Food Aggregators20.0.1.0.0: signed webhooks, a live panel in the till, payouts reconciledDelivery platform orders, straight into your till.A restaurant on three delivery platforms runs three tablets and a cashier who retypes every order. Each platform now posts to a webhook of its own. The order shows up on a live panel in the till, becomes a real POS order when it is accepted, and the monthly payout is checked against the commission you agreed.✓One signed webhook per platform: HMAC-SHA256, Bearer, token only or none✓Prepaid orders are paid in the till with that platform's own payment method✓The payout file is checked line by line against the commission you agreed 102Automated tests, two of them in a real browser4Webhook authentication schemes8Order stages tracked0External libraries why restaurants use itEverything a delivery counter asks forThree tablets, one cashier and a spreadsheet at month end. Now the orders arrive in Odoo and the money is checked against them.From the platformA webhook for each one, and every call on record.One webhook per platformIts own URL and 256-bit token, with a copy button. Orders arrive as plain JSON, the way aggregators post them.Signature checked on the raw bodyHMAC-SHA256, Bearer, token only or none, with the header name you need. Secrets are visible to Point of Sale managers only.Every call is loggedResult, signature check, payload, answer and address, kept for 14 days. A rejected call and a call never made no longer look the same.Retries are harmlessA platform that re-sends an order gets the original back. It never becomes a second ticket in the kitchen.At the tillThe cashier is told, and works the order from one panel.A badge in the navbarA delivery button with the number of open orders, red when one is late. An alert sound can be switched on per till.Orders appear on their ownPushed to the panel as they arrive. No refresh, no polling button.Accept, prepare, ready, picked upOne tap per stage, or Reject. Cards show customer, driver, items, notes and total, and whether it is paid or cash on delivery.Problems stand outA late order and an order with an unmapped item are outlined in red, and the card says why it is stuck.In your booksReal POS orders, and a payout you can check.A real POS orderCreated on acceptance, with the items, the customer's notes and a delivery-fee line if you want one. Taxes come from your own products.Prepaid means paidPaid with the platform's own payment method, so closing the register shows one line per platform. Cash on delivery stays open for the cashier.Nothing is lost overnightAn order accepted while the shop is shut is pushed into the till when the next session opens.Reconcile the payoutImport the platform's CSV and see, order by order, what they paid against what the agreed commission says they owed. at the tillOrders land while the cashier watchesEvery image on this page is a real Odoo 20 Community screen with the module installed. Orders were posted to the real webhook with signed requests. The names, phone numbers and prices are made up, and the platform names are ordinary records you create yourself.It announces itself. A new order raises a notification and the count on the delivery button, with the alert sound if you switched it on. This is the Talabat order that had just been posted to the webhook.What came in overnight. Jahez accepts automatically, so its order was already accepted and was pushed into the till when the session opened. HungerStation is set to wait for a cashier, so its order shows New with Reject and Accept.A cash-on-delivery order is an ordinary open order. Items, the customer's note on the line and the platform reference, customer and phone on the order, plus the delivery fee as its own line. The cashier takes payment when the driver is back.Closing the register. Prepaid orders are already paid with their platform's method, so the closing screen has one line per platform and nothing to explain. the back officeSet a platform up in a few minutesUnder Point of Sale, Configuration: Delivery Platforms, Aggregator Menu, Aggregator Stores and Webhook Log.A platform is one record. Commission, the payment method its orders are paid with, the webhook URL to give them, how they sign, and whether orders are accepted for you. Pause Orders answers callers with a clear no instead of dropping them.The menu, mapped. The platform's SKU and its own item name next to your product. An unknown SKU is matched against internal references, then barcodes, and the match is saved here where you can correct it. work an orderFrom the webhook to a POS orderThe unmapped-item case is the one that stalls a real integration, so it is shown in full.Everything in progress. Total, the commission the platform will keep and the payout you should expect, per order. The red rows are the late order and the order with an item nobody has mapped.An item nobody has mapped. The order is kept and the kitchen can still cook it, but it is held back from the till and the chatter says why. The red line has a Map button.Map, once. The dialog opens with the platform, SKU and name already filled in. Pick the product and save.Then push it to the till. The mapping reaches the orders that were waiting for that SKU, not just the next one. Push to the Till creates the POS order, and the same SKU never stops an order again.Rejecting asks for a reason. Out of stock, kitchen too busy, closing, an address you cannot reach, or other, with a line of detail. It is what you will be shown when the platform asks about it a week later.And it is recorded. The reason and the stage change are on the order's chatter, with who did it and when.A finished order. Every stage is on the chatter. Money shows the items, the delivery fee, the commission and the payout expected from the platform.The POS order it created. A normal paid POS order in the open session, with a Delivery Order button that leads back to where it came from. at month endDid they pay what they owed?Import the payout, see the lines that disagree, and keep a record of the settlement.Upload the platform's file. Their CSV, as they export it. Column names are matched loosely, and you pick the separator.Line by line. Each line is matched to its order by the platform reference. Two lines were paid less than the agreed commission implies (by 3.00 and 1.50), and one pays out for an order that was never received.It will not confirm over a gap. A settlement is what the accounts are read from, so it cannot be confirmed while a line matches no order.Confirmed. With the stray line dropped, the settlement confirms and shows what is still missing: 4.50 less than expected, on the two lines you can see highlighted.Where each payout stands. Reference, platform, period, lines, unmatched and disputed counts, paid out against expected, and status.And the picture by platform. Revenue, commission and expected payout per platform and month, in the usual pivot, graph and list views. evidence and settingsEvery call on recordDid the order reach you? Every call, including the ones that were refused. A bad signature, an unknown token, a paused platform and a store nobody mapped each leave a different line.The evidence. Status, signature verdict, the payload and the answer. A failed call can be replayed once the cause is fixed.Two switches per shop. Settings, Point of Sale: turn the panel on for a till, and decide whether new orders ring. how it worksFrom setup to the payout1Add the platformPoint of Sale, Configuration, Delivery Platforms. Set the authentication, the secret, the commission and a payment method, then map its store id to your shop.2Give them the URLCopy the webhook URL and ask the platform to post to it. Send a test order first to prove the chain without waiting for a customer.3Work the ordersTurn on Delivery Aggregators in the shop settings. Orders appear in the till. Accept, prepare, mark ready and picked up.4ReconcileAt month end, Delivery, Settlements: pick the platform and period, import their file and confirm when every line matches. configurationEverything lives on the platformWebhook URL and tokenGenerated for you, with a copy button. Regenerate Token asks first and stops the old URL working at once.AuthenticationNone, token in the URL only, HMAC-SHA256 signature header, or Bearer token.Shared secretHidden, and readable by Point of Sale managers only. Required for HMAC and Bearer: without it the platform is refused.Signature headerX-Signature by default. A sha256= prefix on the value is accepted.Accept automaticallyOptionally only up to an order total. Off by default for the platform you want a cashier to look at.Push to the TillCreate the POS order as soon as the order is accepted. Turn it off to keep it on the panel until a cashier pushes it.Preparation timeMinutes quoted back to the platform in the webhook answer. 15 by default.Late afterMinutes after which an order that is still open is flagged late. 30 by default.Commission %What the platform keeps. Drives the expected payout and the reconciliation.Payment methodPrepaid orders are paid with it, so the register closes with a line per platform.Delivery fee productMakes the fee a real line on the POS order. Leave empty to leave it off the ticket.StoresEach platform store id mapped to a shop. An empty id is the fallback for a single-branch restaurant. good to knowStraight answersDoes it talk back to the platform?Not on its own. It receives orders on a webhook the platform posts to. The preparation time goes back in the webhook answer, but stage changes are not sent to the platform: there is an empty hook for that, to extend for the platform you use. It does not scrape a site or store your platform login.What do I need from the platform?They have to point their webhook at your URL, which is usually a request to their integrations team. Your Odoo has to be reachable from the internet for that to work.What about an order that arrives at 3 a.m.?It is kept as a record whether or not a till is open. An order that is accepted while the shop is shut, automatically or by a manager, is pushed into the till when the next session opens.What if the platform sends an item I have not mapped?The item is kept and flagged, the order is held back from the till and its card is outlined in red. Open the order, press Map on the line, pick the product, then Push to the Till. Unmapped SKUs are first matched on internal references and barcodes, so this should be the exception.Whose prices are used?The line prices are the ones the platform charged. The till adds the taxes of your own products and fiscal position when it creates the POS order.Their CSV is messy. Will the import cope?Column names are matched across common variants and the separator is yours to choose. Amounts with thousands separators or a currency symbol are read, and dates in year-first, day-first and month-first formats. The file has to be UTF-8.What does a platform see when something is wrong?A wrong token or code answers 404, a wrong signature 401, a paused platform 409, and bad JSON or an unsupported event 400. Anything unexpected, including a store id nobody mapped, answers a generic 500 with no traceback, and the log keeps the real reason so you can fix it and replay the call.Which Odoo edition?Built and tested on Odoo 20 Community. It depends only on Point of Sale and Mail. The webhook needs a URL the platform can reach. supportWe are here to helpWritten and maintained by Aura Odoo Tech.EmailQuestions, problems or a setting you need: write to us directly.odooaura@gmail.comWebsiteMore Odoo modules, documentation and customisation services.www.auraodoo.techHungerStation, Jahez, Talabat and the other platform names are used only as examples of records you create. This module is independent and is not affiliated with or endorsed by any delivery platform.
Key Capabilities & Features
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
Screenshots & Previews
26 images availableExpand Preview
Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.