ConFlowIO
Enquire

ERP

Sage 100

Customers, suppliers, articles, article groups and sales and purchase documents come out with Sage 100's own field names, together with value lists for mapping tables — articles also as Commerce Bundle products, with variants if needed and with the same mapping for every shop.

In the other direction, orders from shops and marketplaces become sales documents of a document type you choose.

Demo on your own data

An order Sage 100 already knows by its number is skipped.

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

Building blocks

Five building blocks for Sage 100

  • Read

    Reads customers, suppliers, articles, article groups and sales and purchase documents with Sage 100's field names, documents with all their items if needed. Plus value lists such as tax classes, revenue codes, payment terms, customer groups, currencies and sales document types for mapping tables.

  • Read articlesRead

    Reads articles as Commerce Bundle products, with variants if needed — ready for the shop building blocks.

  • Write

    Finds customers, suppliers and articles by account number or article number and creates or changes them. Only what the record supplies is changed.

  • Hand over ordersWrite

    Creates orders as sales documents of a type you choose — order confirmation, invoice or delivery note, for example — with net or gross prices or Sage 100's own pricing, shipping costs through a shipping cost article. Orders it already knows are skipped.

  • Free request

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

In practice

Two workflows with Sage 100

  1. Article master data into the shop

    Sage 100 holds the articles; the shop should show the same state.

    1. Triggerschedule
    2. Readarticles from Sage 100, as Commerce Bundle products
    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. Prices and stock come from another source, because Sage 100's API does not supply them.

  2. Orders into the ERP

    Orders from the shop and marketplaces should end up as documents in Sage 100 without manual work.

    1. Triggerthe shop's webhook or a schedule for the marketplaces
    2. Readorders from shop or marketplace
    3. Hand overas a sales document to Sage 100, in the unified order model
    4. Shipping coststhrough a shipping cost article

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

Good to know

What to know about Sage 100

  • PrerequisitesWhat has to be set up on your side.
    • A machine-to-machine application from Sage
    • The dataset released for the API
  • Not coveredLimits of Sage 100's API, not of ConFlowIO.
    • No sales prices and no stock — the API does not supply them
    • Documents cannot be changed once created
    • Variants are read but not created
    • Addresses, payment and shipping method of a document come from the customer in Sage 100
  • 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 Sage 100

Frequent partners

Articles out, orders in.

Contact

See Sage 100 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