ConFlowIO
Enquire

Shop system

Salesforce Commerce Cloud

B2C Commerce is connected through Salesforce's current Admin APIs. Salesforce keeps neither prices nor stock on the product: prices live in price books, stock in inventory lists, texts per locale — the write block serves all three from one record.

Orders come out as Commerce Bundle orders; order, export, payment and shipping status go back.

Demo on your own data

An existing product is never replaced — only what the record names is changed.

  1. Salesforce Commerce CloudShop system
  2. ConFlowIOintegration platformRun active
  3. Akeneo PIM
  4. SAP Business One
  5. Xentral
  • 6ready-made building blocks
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Six building blocks for Salesforce Commerce Cloud

  • Write products and categoriesWrite

    Writes products and categories, with texts in the locale the connection sets. Prices go into a price book, stock into an inventory list. An existing product is never replaced, only changed in the fields the record names.

  • Read dataRead

    Reads products and categories back, products only those changed since the last run if needed.

  • 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.

  • Report back on ordersWrite

    Reports order, export, payment and shipping status back and cancels orders. The tracking number goes into a custom attribute of the order. A status the order already has is not set again.

  • Read customersRead

    Reads the customers of a customer list in the Commerce Bundle's customer model. Names, addresses and contact details only when that is explicitly switched on in the building block.

  • 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 Salesforce Commerce Cloud

  1. Product data from the PIM, prices and stock from the ERP

    The PIM maintains texts and categories, the ERP prices and stock — and Salesforce keeps both apart from the product.

    1. Triggera schedule
    2. Readproducts from Akeneo PIM, prices and stock from SAP Business One, changes only
    3. Maponto the Commerce Bundle, one record per product
    4. Writeproduct, price book and inventory list in Salesforce Commerce Cloud

    One mapping instead of three imports. What was maintained in Salesforce and does not appear in the record is kept.

  2. Orders into the ERP, status back

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

    1. Readorders from Salesforce Commerce Cloud 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. Reportexport and shipping status, the tracking number in the custom attribute

    No order is created twice, and a status the order already has is not set again.

Good to know

What to know about Salesforce Commerce Cloud

  • PrerequisitesWhat has to be set up on your side.
    • An API client from Salesforce's Account Manager
    • For tracking numbers, a custom attribute on the order, created in the shop — the shipping email can use it, for instance
    • A customer list the customers are read from
  • Not coveredPartly limits of Salesforce's API, partly not included as a ready-made building block.
    • Uploading images — the API does not accept them
    • A writable field for tracking numbers — the API has none, hence the custom attribute
    • Creating variants, product options and sets
    • Writing customers — they are only read
    • Reading only what changed since the last run — available for products and orders, not for categories and customers
  • 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 Salesforce Commerce Cloud

Frequent partners

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

Contact

See Salesforce Commerce Cloud 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