Enterprise SMSA Express integration for Odoo — AWB labels, B2C delivery, C2B pickups, COD reconciliation and live tracking across KSA and the GCC. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
Enterprise SMSA Express integration for Odoo — AWB labels, B2C delivery, C2B pickups, COD reconciliation and live tracking across KSA and the GCC.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Odoo 上构建、配置并安装。
约 2–4 周内上线，并提供上线后的支持期。
SMSA Express is the backbone courier for thousands of Saudi and GCC e-commerce sellers — but out of the box, Odoo has no idea it exists. Your team ends up copying addresses into the SMSA portal, printing AWB labels in a second browser tab, pasting tracking numbers back into sales orders by hand, and reconciling COD collections against bank statements days after delivery. Every one of those manual hops is a source of shipping errors, delayed dispatch, and cash that goes untracked.
This is a BUILD-TO-ORDER module. It is not an existing apps.odoo.com download and there is no instant-download link. ECOSIRE designs, develops, installs and supports a production-grade SMSA Express connector tailored to your exact Odoo setup, delivered in a typical 2–4 week lead time. You get real source code you own, wired directly into your delivery, inventory, sales and accounting flows.
Under the hood, the module ships as a proper Odoo addon with its own __manifest__.py declaring dependencies on stock, delivery and sale. It adds a delivery.carrier provider of type "smsa", extends stock.picking with SMSA-specific fields (AWB number, service type, COD amount, pickup reference) via new models.Model classes, and computes shipping rates and COD totals with @api.depends compute methods that stay in sync as order lines change. All SMSA API calls (shipment creation, label retrieval, rate lookup, tracking, pickup booking) run through a dedicated service layer with retry, timeout and structured logging — never blocking the warehouse UI.
Security follows Odoo best practice: access to carrier credentials, COD reconciliation and shipment actions is governed by ir.model.access.csv plus record rules so warehouse operators, finance and admins each see exactly what they should, and multi-company / multi-warehouse setups stay isolated. AWB labels and manifests render as native QWeb reports (thermal 10x15 and A4), printable straight from the picking. Automated actions and scheduled crons keep tracking statuses fresh and flag COD exceptions without anyone clicking a button.
Because it is built on Odoo's standard delivery framework, it works from the sales order, the delivery order, and — where relevant — the eCommerce checkout, and it is exposed over Odoo's XML-RPC / JSON-RPC API so your storefront, WMS or middleware can create SMSA shipments programmatically. It is built and tested against Odoo 17, 18 and 19, on both Community and Enterprise (Enterprise-only features degrade gracefully). ECOSIRE hands over the code, configuration, documentation, training and a post-go-live support window — so you own a maintainable asset, not a black box.
Runs an online store shipping hundreds of orders a day via SMSA Express and needs dispatch, labeling and tracking to happen inside Odoo instead of a separate courier portal, so the warehouse stops double-keying and orders leave faster.
Validates delivery orders, prints AWB labels and books pickups all day. Wants to click 'Validate' on a picking and have the SMSA AWB, label and tracking appear automatically — including bulk label printing for batch transfers.
Owns cash reconciliation and can't afford blind spots on COD. Needs COD amounts captured per shipment, matched against SMSA settlements, and exceptions (shortfalls, un-remitted collections) flagged before month-end close.
Responsible for a maintainable, secure Odoo. Wants a proper addon with clean models, ir.model.access.csv and record rules, sandbox credentials, logs, and XML-RPC access — not a fragile script bolted onto core.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| SMSA Express native integration (AWB creation, labels, tracking) | Purpose-built for SMSA — one-click AWB, QWeb labels, live tracking sync | Possible but you build every API call and edge case yourself | Only if a maintained SMSA-specific app exists for your Odoo version | |
| B2C delivery + C2B pickup + COD in one module | All three workflows delivered and tested together | Whatever you have time to build; COD often skipped | Often partial — many cover delivery but not pickups or COD reconciliation | |
| COD reconciliation against SMSA settlements | Dedicated fields + reconciliation workspace + exception flagging for finance | Manual unless you engineer it | Rarely included; usually just a COD amount field | |
| Fit to your exact Odoo, warehouses and rate rules | Tailored to your setup during the build-to-order engagement | Fully tailored, but at full in-house build cost and risk | Generic — you adapt your process to the app, not the reverse | |
| Source code ownership & maintainability | You own clean, documented source (models, security, reports) | You own it, but quality depends on your team's Odoo depth | Licensed/obfuscated in many cases; limited control | |
| Odoo 17 / 18 / 19 support with upgrade path | Built and tested on 17, 18 and 19 with a supported migration path | You maintain compatibility every upgrade yourself | Depends on vendor keeping the app updated per version | |
| Installation, training and post-go-live support | Install, docs, live training and a support window all included | Your team's time only | Usually self-install with forum/ticket support only | |
| Security via ir.model.access.csv + record rules | Role-scoped access for operators, finance and admins, multi-company safe | Only as rigorous as you make it | Varies by vendor quality |
This is a build-to-order module, so there is no instant download. Typical lead time is 2–4 weeks from kickoff, depending on scope (COD reconciliation depth, custom rate rules, portal tracking, and your Odoo customizations). The flow is: discovery and SMSA account/API review, development and internal testing, installation on your environment with sandbox credentials, end-to-end UAT with your team, then a supervised production go-live. You get progress checkpoints throughout — not a black-box handoff at the end.
Every engagement includes a defined post-go-live support and bug-fix window during which we resolve issues at no extra charge. Because you own the source code, you're never locked in. When SMSA changes its API, or you upgrade Odoo (17 to 18 to 19), or you want new service types, rules or reports, we can extend the module under a maintenance or change-request arrangement. We can also hand over cleanly to your own Odoo team with full documentation if you prefer to maintain it in-house.
The connector is built and tested against Odoo 17, 18 and 19, on both Community and Enterprise. It builds on Odoo's standard delivery framework (delivery.carrier, stock.picking, sale.order), so it fits naturally alongside Inventory, Sales and Accounting. Enterprise-only conveniences degrade gracefully on Community, and the module is written to survive standard version upgrades with a supported migration path.
Yes — all three. B2C forward delivery ships parcels from your warehouse to customers across Saudi Arabia and the GCC. C2B pickup covers reverse logistics and returns, booking SMSA to collect from a customer or supplier and tracking it against the source document. COD is captured as dedicated fields on the shipment (amount, currency, collection status), computed from the order and reconciled against SMSA's settlements, with exception flagging for finance.
Yes. Because it's implemented as native Odoo models, all shipment creation, rate lookup and tracking are available over Odoo's XML-RPC / JSON-RPC API. Your custom storefront, marketplace middleware or WMS can create SMSA shipments, fetch AWB numbers and read live tracking programmatically. We can also wire it into the Odoo eCommerce checkout so shoppers see SMSA rates at checkout where that's relevant to your setup.
Yes. Access to SMSA credentials, shipment actions and COD reconciliation is governed by ir.model.access.csv plus record rules, so operators, finance and admins see only what they should. Each warehouse can hold its own SMSA account number and default service, isolated per company. Credentials are stored in Odoo's configuration (not hardcoded), API calls are logged with structured error handling, and you validate everything against SMSA's sandbox before touching production.
Enterprise SMSA Express integration for Odoo — AWB labels, B2C delivery, C2B pickups, COD reconciliation and live tracking across KSA and the GCC.