ConFlowIO

ERP

weclapp

The cloud ERP weclapp is connected through its standard API. Articles come out as Commerce Bundle products, with the sales price of a sales channel and with stock if needed — and go into every shop with the same mapping.

In the other direction, orders are created as sales orders with the prices paid and shipping costs; processing state and tracking numbers come back.

Demo on your own data

An order weclapp already knows by its number is skipped.

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

Building blocks

Seven building blocks for weclapp

  • Read articlesRead

    Reads articles as Commerce Bundle products, in full or only those changed since the last run, with the sales price of a sales channel and with stock if needed.

  • Read stockRead

    Reads stock as lean records. An article without a stock figure is skipped rather than reported as zero.

  • Hand over ordersWrite

    Creates orders as sales orders with the prices paid and shipping costs. Known orders are skipped, missing customers created.

  • Read sales ordersRead

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

  • Cancel sales ordersWrite

    Cancels the sales order when the order was cancelled in the shop — as long as it has been neither shipped nor invoiced.

  • Read master data and documentsRead

    Reads, with weclapp's field names, customers, suppliers, invoices with payment status, quotations, shipments, prices, stock levels and master data such as payment and shipping methods.

  • Free request

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

In practice

Two workflows with weclapp

  1. Articles and stock into the shop

    weclapp holds articles and stock; the shop and marketplaces should show the same state.

    1. Triggerschedule
    2. Readarticles from weclapp, with the sales price of a sales channel
    3. Change detectiononly what changed goes on
    4. WriteShopware 6, Shopify or WooCommerce

    One mapping onto the Commerce Bundle, and the last building block decides which shop is written. An article without a stock figure does not report a stock of zero.

  2. Orders into the ERP — and back

    Orders from the shop and marketplaces should end up as sales orders in weclapp without manual work, with the shipment report to follow.

    1. Triggerthe shop's webhook or a schedule for the marketplaces
    2. Hand overas a sales order to weclapp, missing customers are created
    3. Read backprocessing state and tracking numbers
    4. Reportthe shipment to shop and marketplace

    No order is re-entered by hand, none is created twice — an order weclapp already knows is skipped.

Good to know

What to know about weclapp

  • PrerequisitesWhat has to be set up on your side.
    • The API token of a weclapp user
    • The sales channel whose sales price should go into the shop
  • Not coveredWhat ConFlowIO does not write to weclapp.
    • Articles are read but not written to weclapp
    • The same goes for stock and prices — they come out of weclapp, not in
    • A sales order is cancelled only as long as it has been neither shipped nor invoiced
  • 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 weclapp on your own data

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