A build-to-order WooCommerce extension that connects your store to enterprise procurement systems via cXML/OCI punchout and EDI document exchange, built and installed for you by ECOSIRE. One-time license from $799.00 USD for WooCommerce (build-to-order) — includes 12 months of updates and support.

A build-to-order WooCommerce extension that connects your store to enterprise procurement systems via cXML/OCI punchout and EDI document exchange, built and installed for you by ECOSIRE.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Enterprise buyers don't shop your storefront — they buy through Ariba, Coupa, Jaggaer and SAP procurement portals. To win those accounts, your WooCommerce store has to speak their language: cXML/OCI punchout for catalog browsing and EDI X12 documents for the order lifecycle. WooCommerce core has none of this, and the off-the-shelf B2B plugins on WooCommerce.com stop at wholesale pricing and quote forms — they don't issue a cXML PunchOutSetupResponse or post an 856 ASN back to a buyer's ERP.
cXML punchout: standards-compliant PunchOutSetupRequest/Response, edit/inspect session handling, and PunchOutOrderMessage cart return to the buyer's requisition
OCI (Open Catalog Interface) punchout for SAP-based procurement systems, with the HOOK_URL round-trip and field mapping configured for your catalog
EDI X12 document exchange: inbound 850 purchase order to WooCommerce order, outbound 855 acknowledgement, 856 advance ship notice, and 810 invoice
Procurement-system integration profiles for Ariba Network, Coupa and similar platforms (shared-secret/credential auth, identity domains, AuxiliaryID handling)
Customer-specific catalogs and contract pricing resolved per punchout organization, so each enterprise buyer sees their negotiated SKUs and rates
PO-based / net-terms checkout that bypasses card capture for approved accounts and records the buyer's purchase-order number on the order
This is a build-to-order connector: ECOSIRE designs, builds, installs and supports it directly on your WordPress site. We register the punchout endpoints as custom REST routes alongside the WooCommerce REST API, store buyer organizations and trading-partner profiles in custom post types / custom tables, and hook the order lifecycle through WooCommerce actions and filters (woocommerce_checkout_order_processed, woocommerce_order_status_changed) to emit and ingest EDI. It is fully HPOS-compatible (custom order tables) and works on WPML/multisite installs.
What it does: authenticated cXML and OCI punchout so a buyer punches out from their procurement system into your live WooCommerce catalog and returns a cart back to their requisition; EDI 850/855/856/810 exchange (inbound purchase order → order, outbound acknowledgement, advance ship notice, and invoice); customer-specific catalogs and contract pricing keyed to the punchout organization; and PO-based checkout that bypasses card payment for approved net-terms accounts.
Because every procurement integration is specific — your trading partners, your transport (HTTPS POST, AS2, SFTP/VAN), your price lists — we scope it to your setup rather than shipping a generic download. You get a tested connector, documentation, and a support window. Honest delivery: this is custom engineering with a real lead time, not an instant marketplace install.
Runs a WooCommerce catalog and keeps losing or manually servicing large accounts because those buyers mandate punchout and EDI. Needs to appear inside Ariba/Coupa and exchange POs and invoices electronically to keep the contract.
Tired of re-keying purchase orders that arrive as PDFs or EDI files into WooCommerce by hand. Wants inbound 850s to create orders automatically and 855/856/810 to flow back without spreadsheets, with a log to audit every transaction.
Owns the WordPress/WooCommerce stack and is being asked by a big customer's procurement team for a punchout URL and EDI spec. Wants a maintained, HPOS-compatible integration built and supported by specialists rather than a fragile in-house script.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 B2B Punchout & EDI Connector for WooCommerce 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 B2B Punchout & EDI Connector for WooCommerce,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| cXML/OCI punchout from procurement portals (Ariba, Coupa, SAP) | ||||
| EDI 850/855/856/810 document exchange | ||||
| Customer-specific catalogs & contract pricing per buyer organization | ||||
| PO-based / net-terms checkout without card capture | ||||
| HPOS-compatible, standards-based WooCommerce integration | ||||
| Built, installed & supported for you with a defined support window | ||||
| Instant self-service download & activation | ||||
| Configured to your specific trading partners' EDI specs & transport (AS2/SFTP/VAN) |
No. This is a build-to-order connector. ECOSIRE designs, builds, installs and configures it directly on your WordPress/WooCommerce site for your specific trading partners and procurement systems. There is no instant marketplace download — punchout and EDI integrations depend on your partners' credentials, document specs and transport, which we scope and test per project.
A typical engagement runs about 3 to 6 weeks from kickoff, depending on how many trading partners, document types (850/855/856/810) and punchout flavors (cXML vs OCI) are in scope and how quickly your procurement partner provides test-environment access and EDI specs. We confirm a concrete timeline after a short scoping call, and a single-partner cXML-only punchout is on the faster end.
Every build includes a post-launch support window for bug fixes, trading-partner onboarding help, and compatibility with WooCommerce and WordPress updates during that period. We test against HPOS and current WooCommerce releases. Ongoing maintenance and additional trading partners or document types can be added under a support retainer or as a follow-on scope.
On the punchout side we support cXML (Ariba Network, Coupa and other cXML-capable platforms) and OCI for SAP-based systems. On the EDI side we implement the core order lifecycle in X12 — 850 purchase order, 855 acknowledgement, 856 advance ship notice and 810 invoice. Other documents (e.g. 832 catalog, 820 remittance) or EDIFACT can be added as scoped extensions.
Yes. The connector is built to WooCommerce and WordPress standards — custom REST API routes, custom post types/tables, and the standard order action/filter hooks — so it does not depend on a particular theme. It is HPOS (High-Performance Order Storage) compatible and WPML/multisite aware. During scoping we review your active plugins (payment gateways, B2B/wholesale, ERP sync) to avoid conflicts before we build.
A build-to-order WooCommerce extension that connects your store to enterprise procurement systems via cXML/OCI punchout and EDI document exchange, built and installed for you by ECOSIRE.