This is a build-to-order module, not an instant apps.odoo.com download — there is no ZIP that installs the moment you pay. Typical delivery is one working week depending on how many payment providers, carriers, and custom fields your store needs. After a short kickoff to confirm your Odoo version, theme, and providers, we build on a branch, deliver to staging for your review, then schedule the production rollout with you. You receive the full source at handover.

Every build includes a post-launch support window covering bug fixes and adjustments under an agreed SLA, with a named ECOSIRE contact. Because you own the complete module source, your own team can also maintain it. When you later upgrade Odoo (for example 18 to 19), we offer a compatibility pass to re-test and adjust the checkout for the new version. Ongoing support or a retainer can be arranged beyond the initial window.

Yes. The module overrides the standard website_sale checkout but writes to the same sale.order, res.partner, and payment records Odoo already uses. Your pricelists, fiscal positions, tax computation, delivery carriers, and back-office order pipeline all keep working — totals are recomputed and authoritatively re-validated server-side, so nothing about your accounting or inventory flow changes except the checkout screen itself.

It is built and tested against Odoo 17, 18, and 19, on both Community and Enterprise. We target the specific version you run and note the differences (some payment provider modules and features differ between Community and Enterprise), so you get a build matched to your exact environment rather than a lowest-common-denominator template.

Express wallet buttons are surfaced through your existing Stripe or Adyen payment.provider configuration in Odoo. As part of delivery we handle the domain verification and wiring so Apple Pay / Google Pay appear at the top of the checkout for eligible shoppers, letting returning and mobile customers pay in a couple of taps. If a provider is temporarily unavailable, the flow falls back cleanly to standard payment so a sale is never blocked.

Yes. Access is enforced with ir.model.access.csv and record rules so a shopper can only read and write their own draft order — there is no cross-customer exposure. Card data is never stored in the module; payments run through your PCI-compliant provider and, for saved cards, Odoo's standard payment.token records. Client-side validation is convenience only; the server always re-validates the order before confirmation.