Foodics Connector | Sync Foodics POS with Odoo 19
by Moaz Nabil https://github.com/moaaznaabilali$ 50.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Point of Sale (point_of_sale) |
| Lines of code | 1485 |
| Technical Name |
mn_foodics_connector |
| License | OPL-1 |
| Website | https://github.com/moaaznaabilali |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Point of Sale (point_of_sale) |
| Lines of code | 1485 |
| Technical Name |
mn_foodics_connector |
| License | OPL-1 |
| Website | https://github.com/moaaznaabilali |
| Versions | 17.0 18.0 19.0 |
Foodics → Odoo.
Done right. At $50.
Complete Foodics POS sync for Odoo 17 — branches, products, customers, payment methods, end-of-day Z-report posting, ZATCA Phase 2 passthrough, real-time webhooks. MENA-first. Built by a Saudi developer who shipped the Salla & Amazon connectors too.
| CONNECTOR | PRICE | v19 | ZATCA | SCOPE |
|---|---|---|---|---|
| qs_foodics | $1,625 | ✖ | ✖ | Full · v16-17 only |
| wt_foodic (Warlock) | $298 | ✔ | ✖ | Full · English-only |
| Digital Economics | $59 | ✖ | ✖ | Auth only · “phase 1” |
| mn_foodics_connector | $50 | ✔ | ✔ | Complete + Arabic + Mada/Tabby/Tamara |
Foodics runs your restaurant.
Odoo runs your business. Connect them.
F&B chains in KSA, UAE and Egypt run Foodics for the POS — ZATCA-cleared invoices, real-time kitchen routing, multi-branch. But their books, payroll, purchasing, vendors and consolidated P&L live in Odoo. Without a connector, somebody copies numbers between the two every night. With this connector, the sync runs at midnight — one journal entry per branch per day, every order archived with its ZATCA UUID, every webhook event logged. Build your books once. Forget about it.
Your books outgrow Foodics-only reporting fast.
Foodics dashboards are excellent at the till level. They're not your books. When you scale past a few branches, you need consolidated P&L in Odoo, vendor payables in Odoo, payroll in Odoo, and a single audit trail tied to your ZATCA filings. This connector makes Foodics the data source and Odoo the system of record — without you copy-pasting anything.
3 minutes from token to first sync.
Open Foodics → Connect. Paste a Personal Access Token from your Foodics console. Pick sandbox or production. Click Connect & Test. We hit /v5/business and either flip the account to active or surface the exact API error. Then Pull Master Data in one click: branches, categories, products, customers, payment methods — all logged in the Sync Logs with row counts and timing.
Mada · Tabby · Tamara · STC Pay — out of the box.
Payment methods sync from Foodics with preset hints already picked: Cash, Mada, Card, Tabby, Tamara, STC Pay. Each one carries the Arabic name (ÙÙد٠/ ٠د٠/ تاب٠/ ت٠ارا) so your accounting team reads what their POS team reads. Then you map each method to an Odoo journal — the Z-report knows where to land each currency stream. ZATCA UUIDs are pulled into account.move so Odoo's books reference the authoritative Foodics-cleared invoice.
Webhooks, rate limits, audit trails.
Every webhook from Foodics is logged with HMAC-SHA256 signature verification — invalid signatures still get recorded for forensics, but trigger zero side effects. Every sync run logs created / updated / failed counts and duration. The REST client honours Foodics' X-RateLimit-Remaining and Retry-After headers with exponential backoff. No 429 storms, no silent failures.
What ships in the box.
Built for Odoo 17. Community + Enterprise.
$50. Install in 10 seconds.
Pays for itself the first night someone doesn’t copy yesterday’s Foodics totals into Odoo by hand. Same pricing as the “phase 1 skeleton” competitor — with a complete v1 instead.
Built by Moaz Nabil · Odoo 17 Community + Enterprise · OPL-1
moaaznaabilali@gmail.com · github.com/moaaznaabilali
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module