ConFlowIO
Enquire

Product information and master data

Stibo Systems STEP

Products are read below a node, an object type or by a search condition, per context — per language, say — in the working or the approved state. They come out with categories, product relations and images as Commerce Bundle products and from there go into every shop; a classification hierarchy becomes the category tree.

In the other direction, products are created and changed from the ERP or supplier data. Large volumes go through STEP's import and export configurations. STEP is connected on your own servers as well as as SaaS from Stibo.

Demo on your own data

Only the mapped attributes are written — all others stay in STEP as they are.

  1. Stibo Systems STEPProduct information and master data
  2. ConFlowIOintegration platformRun active
  3. Shopware 6
  4. Shopify
  5. Adobe Commerce
  • 7ready-made building blocks
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Seven building blocks for Stibo Systems STEP

  • Read productsRead

    Reads products below a node, an object type or by a search condition, per context and in the working or the approved state — as Commerce Bundle products with categories, product relations and images. A mapping table sets which attribute fills which product field.

  • Read classificationsRead

    Reads a classification hierarchy as the category tree.

  • Read dataRead

    Reads supplier, customer or other master data in STEP's own form.

  • Write productsWrite

    Creates or changes products in STEP from the ERP or supplier data, only the mapped attributes, with approval if you wish.

  • Start importWrite

    Hands a file, such as STEPXML, to one of STEP's import configurations — for large volumes.

  • Start exportRead

    Starts one of STEP's export configurations and fetches its file — including the changes since the last run that the export selects.

  • Free request

    For everything there is no ready-made building block for: a request to the API, with the stored credentials.

In practice

Two processes with Stibo Systems STEP

  1. Product data from STEP into the shop

    STEP holds the products; the shop shows the approved state.

    1. Triggerschedule
    2. Readthe classification hierarchy as the category tree
    3. Readproducts from STEP, per language, in the approved state
    4. WriteShopware 6, Shopify or another shop

    One mapping onto the Commerce Bundle; a second shop is one more target building block.

  2. Master data into STEP

    New products are created in the ERP or arrive with a supplier's data.

    1. Triggerschedule
    2. Readarticles from the ERP or supplier data
    3. Writeproducts into STEP, only the mapped attributes, with approval if you wish
    4. Large volumesas a file to one of STEP's imports

    Attributes without a mapping stay in STEP as they are.

Good to know

What to know about Stibo Systems STEP

  • PrerequisitesWhat has to be set up on your side.
    • A STEP user with access to the API
    • For SaaS, alternatively a client set up by Stibo
  • Not coveredSo you know where you stand.
    • Reading only the changes since the last run goes through an export that STEP selects — not through reading products
    • Attributes without a mapping are not changed when writing
  • 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 Stibo Systems STEP

Frequent partners

Products out, master data in.

Contact

See Stibo Systems STEP on your own data

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

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