ConFlowIO

ERP

Xentral

Articles come out of Xentral as Commerce Bundle products, in full or only those changed since the last run — and go into every shop with the same mapping.

In the other direction, orders are created as released sales orders with the prices actually paid. On top come customers, invoices and documents, offers and returns, prices and stock, purchase orders, goods receipts and supplier invoices.

Demo on your own data

An order Xentral already knows by its number is skipped.

  1. XentralERP
  2. ConFlowIOintegration platformRun active
  3. Shopware 6
  4. Shopify
  5. Amazon
  • 18ready-made building blocks
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Eighteen building blocks for Xentral

  • Read articlesRead

    Reads articles as Commerce Bundle products, in full or only those changed since the last run.

  • Read stockRead

    Reads stock as lean records that touch only the stock in the shop. An article without a stock figure is skipped rather than reported as zero.

  • Hand over ordersWrite

    Creates orders as released sales orders with the prices paid. Known orders are skipped; missing customers are created on request.

  • Read sales ordersRead

    Reads sales orders back with processing state and tracking numbers, to report the shipment to the shop or marketplace.

  • Change sales ordersWrite

    Changes sales order headers without touching the line items.

  • Cancel sales ordersWrite

    An order cancelled in the shop cancels the sales order in Xentral. A sales order already cancelled is skipped.

  • Create invoicesWrite

    Creates the invoice for sales orders in Xentral.

  • Documents as PDFRead

    Loads documents as a PDF that moves on through the workflow as a file.

  • Create offersWrite

    Creates offers. Whatever already exists is recognised.

  • Create returnsWrite

    Creates returns. Whatever already exists is recognised.

  • Write pricesWrite

    Writes sales and purchase prices.

  • Book stockWrite

    Books stock onto a storage bin or sets it to a counted quantity.

  • Purchase ordersWrite

    Creates purchase orders with suppliers. Whatever already exists is recognised.

  • Book goods receiptWrite

    Books goods receipts.

  • Record supplier invoicesWrite

    Records supplier invoices with their receipt. Whatever already exists is recognised.

  • Write customersWrite

    Finds customers by customer number, email address or identifier and creates or changes them, never twice — with billing address, delivery addresses and contact persons.

  • Read master data and documentsRead

    Fetches, with Xentral's own field names, whatever has no counterpart in the Commerce Bundle: customers, suppliers, invoices with payment status and dunning level, credit notes, all sales prices, returns, purchase orders and master data such as tax rates, payment methods and shipping methods. Invoices, returns and purchase orders also only those changed since the last run.

  • Free request

    For anything without a ready-made building block: a request to the API, using the stored credentials.

In practice

Two workflows with Xentral

  1. Stock and prices every hour

    Xentral holds the stock; several sales channels have to follow.

    1. Triggerhourly
    2. Readstock from Xentral, page by page
    3. Change detectionpass on only what changed
    4. ChannelsShopware 6, Shopify, Amazon, eBay, OTTO Market, TB.One

    Of 200,000 articles a few hundred change every hour; only those are written. The hourly rhythm stays a business decision rather than a question of cost.

  2. Orders into the ERP — and back

    Orders from shop and marketplaces should reach the ERP without delay, with shipping and invoicing following without manual work.

    1. Triggerthe shop's webhook, or a schedule for the marketplaces
    2. Hand overas a sales order to Xentral, in the unified order model
    3. Shiplabel from the carrier, invoice in Lexware Office
    4. Reporttracking number back to shop and marketplace

    No order is lost, none is re-entered by hand, none is created twice. If the run fails for good, a message goes out, and the overview says which order it concerns.

Good to know

What to know about Xentral

  • PrerequisitesWhat has to be set up on your side.
    • Access to Xentral's API
    • The credentials are stored encrypted in ConFlowIO
  • Not coveredWhat the building blocks deliberately do not do.
    • Sales order headers are changed, line items are left untouched
    • A sales order already cancelled is not cancelled again
    • Whatever has no counterpart in the Commerce Bundle comes with Xentral's field names rather than as a Commerce Bundle data model
  • 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

Contact

See Xentral on your own data

We are glad to show ConFlowIO on your own data. Bring a real slice of 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