ConFlowIO
Enquire

Shop system

Shopware 6

The most extensive integration in ConFlowIO, because it is the one asked for most often. It writes in batches and bridges your article numbers and Shopware 6's internal identifier — so a second run hits the same products instead of creating them again.

Orders come out as Commerce Bundle orders. Status, shipments with tracking numbers, documents and refunds go back into the shop.

Demo on your own data

An order that already has the requested state is skipped — so the report-back can be repeated safely.

  1. Shopware 6Shop system
  2. ConFlowIOintegration platformRun active
  3. Xentral
  4. Pimcore
  5. Shopware 5
  • 16ready-made building blocks
  • 32-character internal identifier that ConFlowIO maps your article number onto
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Sixteen building blocks for Shopware 6

Every building block brings the groundwork and the safeguards a free call does not have.

  • Write products, categories and master dataWrite

    Writes in batches of configurable size and takes product images along. The article number is mapped onto the shop's internal identifier; assignments such as categories, properties, images and visibilities can be replaced completely if needed, with a safety limit.

  • Read dataRead

    Reads data back from Shopware 6, only what changed since the last run if needed — as the source for a reconciliation or a migration, say.

  • Media libraryWrite

    Maintains the Shopware 6 media library as a building block of its own.

  • Upload filesWrite

    Uploads arbitrary files to the shop.

  • Bulk deletion with a safety limitWrite

    Deletes at most a configurable share of the stock. By default it only determines what it would delete — a dry run before anything disappears.

  • Control indexingWrite

    Switches indexing off for the duration of an import and triggers it deliberately afterwards.

  • 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. Payment and shipping method and tracking numbers come along; an order also counts as changed when only its items, deliveries or payments changed. Reading in a chosen language of the shop is possible.

  • Set order statusWrite

    Sets order, payment and delivery status separately, cancellation included — per order and with the shop's email if needed. An order that already has the state is skipped.

  • Report shipmentWrite

    Stores the tracking numbers on the delivery, partial shipments included.

  • Create documentsWrite

    Creates the invoice, delivery note, credit note, cancellation invoice and e-invoice in the shop and hands them on as files.

  • RefundsWrite

    Refunds items or an amount through the payment method that was used. 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.

  • Write tier and customer-group pricesWrite

    Writes tier and customer-group prices and matches them to the shop's price rules by name.

  • Read promotionsRead

    Reads promotions and their redemptions.

  • Free API callFree request

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

In practice

Two workflows with Shopware 6

  1. Supplier catalogue into the shop

    40 suppliers, each with their own format and their own rhythm.

    1. Triggera schedule, or a file arriving over SFTP
    2. ReadBMEcat, CSV or Excel, per supplier
    3. Macropricing logic and checks, the same for all of them
    4. WriteShopware 6, in batches

    A new supplier is connected in a morning rather than in a sprint. A change to the pricing logic applies at once to all forty imports.

  2. Orders into the ERP, shipments back into the shop

    Orders should reach the ERP without manual work, and the tracking numbers get back to the order.

    1. Readopen orders from Shopware 6 that changed since the last run
    2. Hand overas a sales order to Xentral, in the unified order model
    3. Read backprocessing state and tracking numbers from Xentral
    4. Reportshipment with tracking number on the delivery in Shopware 6

    No order is re-entered by hand, none is created twice. An order that already has the reported state is skipped.

Good to know

What sets Shopware 6 apart

  • How Shopware 6 sees a productConFlowIO handles the peculiarities so your mapping does not have to rebuild them.
    • Recognised by a 32-character internal identifier
    • Price on the product, as a price list per currency
    • Stock on the product
  • Protection against the big mistakeLimits before a run writes or deletes on a large scale.
    • Bulk deletion with a maximum permitted share of the stock
    • A dry run before anything disappears
    • A change limit on the writing building block
    • An approval building block that holds the run until someone approves
  • 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 Shopware 6

Frequent partners

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

Contact

See Shopware 6 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