ConFlowIO
Enquire

Shop system

WooCommerce

Connected through WooCommerce's REST API, over HTTPS only. Products are found by SKU and written in batches of 100; whether prices are entered with or without tax, and which units weight and dimensions are kept in, ConFlowIO reads from the shop and converts, rather than guessing.

Orders come out as Commerce Bundle orders. Status, payment, tracking number and cancellation go back, and refunds on top.

Demo on your own data

A refund is recorded in the shop with a reference of its own and never triggered twice.

  1. WooCommerceShop system
  2. ConFlowIOintegration platformRun active
  3. Xentral
  4. Pimcore
  5. Lexware Office
  • 9ready-made building blocks
  • 100products per batch
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Nine building blocks for WooCommerce

  • Write products, categories and master dataWrite

    Writes products by SKU, in batches of 100. Categories are found by a short name derived from the category number.

  • Read dataRead

    Reads data back from WooCommerce, only what changed since the last run if needed.

  • Read ordersRead

    Reads orders as Commerce Bundle orders — with items, billing and shipping address and processing state, only the open ones and only those changed since the last run if needed.

  • Report back on ordersWrite

    Sets status and payment and cancels orders; states added by an extension when explicitly requested. Tracking numbers go out as a customer note, which WooCommerce stores on the order and sends by email — optionally also into the Shipment Tracking extension.

  • RefundsWrite

    Refunds an amount or items; whether the payment provider pays out is an explicit choice. A refund always needs an explicit statement of what is refunded, is recorded in the shop with a reference of its own and is never triggered twice.

  • Read customersRead

    Reads customer accounts in the Commerce Bundle's customer model. Names, addresses and contact details are read only when that is explicitly switched on in the building block.

  • Write customersWrite

    Creates or changes customer accounts from the Commerce Bundle's customer model.

  • Set up webhooksWrite

    Sets up webhooks in the shop from within the workflow, instead of creating them by hand.

  • Free API callFree request

    Reaches everything the shop's API offers — just without the groundwork and the safeguards of a ready-made building block.

Product images are handed over as an address — only for products that have none yet, because WooCommerce copies every image into its media library.

In practice

Two workflows with WooCommerce

  1. Supplier catalogue into the shop

    The supplier drops a catalogue overnight; by morning the range is in the shop.

    1. Triggera schedule
    2. ReadBMEcat, CSV or Excel over SFTP
    3. Maponto the Commerce Bundle
    4. WriteWooCommerce, in batches of 100

    Prices arrive in the shop the way the shop expects them — with or without tax.

  2. From order to invoice

    Every order should produce an invoice without anyone typing it.

    1. Triggera webhook, set up in the shop from within the workflow
    2. Readnew orders from WooCommerce
    3. Invoicein Lexware Office, finalised with a PDF
    4. Reportstatus and payment back to WooCommerce

    An order that already has an invoice is skipped, and so is a report-back whose state the shop already holds.

Good to know

What to know about WooCommerce

  • How WooCommerce sees a productMuch depends on the shop's settings; ConFlowIO reads them.
    • Recognised directly by the SKU
    • Price on the product — net or gross, depending on the tax setting
    • Stock on the product, only with stock management enabled
  • Not coveredNot included as a ready-made building block — or not provided for by WooCommerce.
    • Variants, tax rates and manufacturers
    • Partial shipments as a ready-made building block
    • A field of its own for tracking numbers — WooCommerce has none, hence the customer note
  • DurabilityApplies to this integration as to every workflow in ConFlowIO.
    • Failed steps retry themselves
    • Large reads are processed page by page, each page a step of its own
    • A failed run is continued rather than started over
    • Live logs per step, with credentials removed

Works well with

What works with WooCommerce

Frequent partners

All of them speak the same data model, the Commerce Bundle.

Contact

See WooCommerce on your own data

We are glad to show ConFlowIO on your own data. Bring a real slice of your catalogue or your orders.

The difference shows at real volumes — not at five sample records.

Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.

Rather write directly?info@conflowio.com