Running Square POS in the shop and Odoo in the back office means keeping two versions of the truth. Somebody exports a Square sales report at the end of the day and keys the totals into Odoo, or a script drops a CSV into the accounting inbox. Stock is the worst part: Odoo's stock.quant figures drift away from what the till has actually sold, so replenishment rules fire late, purchase suggestions are wrong, and the online channel oversells items that walked out the door hours ago. When the Square payout lands, it is a net figure — gross sales, minus processing fees, minus refunds, plus tips — and reconciling one bank line against dozens of individual orders is manual work that quietly gets skipped. Odoo out of the box has no Square knowledge at all: there is no Square provider in the payment framework, no catalog mapping, and no stock.quant listener that pushes availability to a Square location.

What we build is a proper Odoo module that speaks Square's REST API on your behalf. A dedicated square.backend model holds credentials, the location IDs you trade from, and per-backend sync toggles; OAuth tokens are stored encrypted and refreshed automatically rather than pasted into a config file. Orders arrive either by Square webhook (order.updated, payment.updated, refund.created) hitting an authenticated controller route, or by a scheduled ir.cron catch-up poll for anything the webhook missed. Each Square order maps to a sale.order — or straight to an invoice, depending on how you want revenue recognised — with a unique square_order_id index so a replayed webhook can never create a duplicate. Fulfilment and payment state map onto a configurable status table, so a Square COMPLETED order can land as a confirmed and delivered sale while an OPEN tab stays a draft.

Catalog and stock run in both directions. Odoo product.template and product.product records export to Square catalog objects with your category tree, variant attributes, SKUs, images and tax codes carried across; a mapping model keeps the Square object ID and version so updates use Square's optimistic-concurrency version field instead of blindly overwriting. Stock synchronisation hooks stock.quant changes through a compute/@api.depends chain plus a debounced queue job, so a receipt in Odoo pushes fresh availability to the right Square location within seconds rather than on a nightly batch, and a till sale writes back down the same path. Price and pricelist changes follow the same route, with a dry-run mode so you can see exactly what would change before anything is written. Where you ship rather than hand over the counter, shipment confirmation and tracking numbers push back to Square so the customer record stays complete.

Settlements are handled as accounting, not as a report. We pull Square's payouts and payout entries, then generate account.move entries that split gross sales, processing fees to your fee expense account, refunds, tips and adjustments per your chart of accounts and fiscal position — landing on a dedicated journal so the payout line on the bank statement reconciles against one balanced entry. Everything is instrumented: a sync log model holding the raw request and response, a Retry action on failed records, and a QWeb reconciliation report you can hand to your accountant. Access is governed by ir.model.access.csv plus record rules so a shop manager sees their own location's data and nothing else, and the whole module is multi-company aware.

This is a build-to-order product, not an instant download. You request a quotation, we run a short scoping call, and we write down exactly which Square locations, which order and fulfilment states, which accounts and which Odoo version we are targeting. From confirmed scope, typical delivery is 2-4 weeks: we develop against your Odoo version (17.0, 18.0 or 19.0, Community or Enterprise), install on a staging copy of your database, run UAT against the Square sandbox or a limited live location, then go live with a rollback plan. You receive the full source, a git repository handover, technical and user documentation, a training session and a post-go-live support window. Nothing is obfuscated — you own the code we write for you.