Sage 100 (US) to Shopify (CRMPro)

This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-shopify/erps/sage-100-us". It extends the dlake-crmpro-shopify skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-100-us-shopify/.

CRMPro → Shopify — Sage 100 (US): what the shipped templates set up

This is a capability summary, not an operating guide. To receive the operational skill you must be a registered, whitelisted Commercient customer. Whitelisted customers fetch it with dlake admin get_skill dlake-crmpro-shopify/erps/sage-100-us (or list_skills) against the Commercient admin plane. Existing customers who need access or help: contact support@commercient.com. New customers: contact sales@commercient.com to become a customer and be whitelisted.

dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. Read it first; this page does not repeat it. dlake-crmpro-shopify is the destination skill this page is a child of, and the authority for the Shopify conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page grows as the catalogue does.

1. What the templates deliver

Group	Business outcome	Objects	Source tables and views
Create Customer	The templates push Customer to Shopify.	Customer	customers
Create Customer Address	The templates push Customer address to Shopify.	Customer address	countries, customers
Create Product	The templates push Product object to Shopify.	Product object	items
Create Order	The templates push Order to Shopify.	Order	countries, sales order headers, customers, sales order history headers
Create Order Shipping Address	The templates push Order shipping address to Shopify.	Order shipping address	countries, sales order headers, customers, sales order history headers
Create Order Billing Address	The templates push Order billing address to Shopify.	Order billing address	countries, sales order headers, customers, sales order history headers
Create Order Line Item	The templates push Order line item to Shopify.	Order line item	sales order lines, sales order headers, sales order history lines, sales order history headers
Customer	The templates push Customer to Shopify. Records are created once; they are not updated and none are deleted.	Customer	customers
Customer Address	The templates push Customer address to Shopify. Records are created once; they are not updated and none are deleted.	Customer address	countries, customers
Product object	The templates push Product object to Shopify. Records are created once; they are not updated and none are deleted.	Product object	items
Product object update	The templates push Product quantity, Product price to Shopify. Existing records are updated only — nothing is created and nothing is deleted.	Product quantity, Product price	items, Shopify product variants (mirrored), Shopify inventory levels (mirrored)

2. The process rows the templates create

Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.

Display name	Destination object	Run sequence
Create Customer	Customer	1
Create Customer	Customer	1
Create Product	Product object	1
Update Quantity	Product quantity	1
Update Price	Product price	1
Create Customer Address	Customer address	2
Customer address	Customer address	2
Create Product	Product object	3
Create Order	Order	5
Create Order Shipping Address	Order shipping address	6
Create Order Billing Address	Order billing address	7
Create Order Line Item	Order line item	8

Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.

3. The views

“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.

View	Change detection	Source tables
new customer feed	insert only	customers
new customer feed	insert only	customers
new product feed	insert only	items
product quantity update feed	—	items, Shopify product variants (mirrored), Shopify inventory levels (mirrored)
product price update feed	—	items, Shopify product variants (mirrored)
new customer address feed	insert only	countries, customers
new customer address feed	insert only	countries, customers
new item feed	insert only	items
new order feed	insert only	countries, sales order headers, customers, sales order history headers
new order shipping address feed	insert only	countries, sales order headers, customers, sales order history headers
new order billing address feed	insert only	countries, sales order headers, customers, sales order history headers
new order line item feed	insert only	sales order lines, sales order headers, sales order history lines, sales order history headers

4. Order of work

The templates set run sequence to 1, 2, 3, 5, 6, 7, 8. A run processes active rows in ascending run sequence, which is the order the templates put them in:

1 — Create Customer, Create Product, Update Quantity, Update Price
2 — Create Customer Address, Customer address
3 — Create Product
5 — Create Order
6 — Create Order Shipping Address
7 — Create Order Billing Address
8 — Create Order Line Item

Several of these rows share a run sequence value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.

new customer address feed reads new customer sync output
new order feed reads new customer sync output
new order shipping address feed reads new order sync output
new order billing address feed reads new order sync output
new order line item feed reads new order sync output, new item sync output, new item variant sync output; no template in this set writes new item variant sync output
new customer address feed reads new customer sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

Template	Object	Mapped fields	First ERP → Shopify pairs
Create Customer	Customer	11	AR division number, Customer number → record key, AR division number, Customer number → description, AR division number, Customer number → ERP code, Email address → Email, Customer name → Given name
Create Customer	Customer	10	record key → record key, description → description, ERP code → ERP code, Email → Email, Given name → Given name
Create Product	Product object	6	Item description → Title, Item description → Product body text, Item code → record key, Item code → Stock keeping unit, Standard unit price → Price
Update Quantity	Product quantity	5	product variant identifier → Id, Total quantity on hand → Inventory quantity, inventory item identifier → inventory item identifier, Inventory quantity → Previous quantity, Location identifier → Location identifier
Update Price	Product price	2	Item code → product variant identifier, Standard unit price → Price
Create Customer Address	Customer address	21	AR division number, Customer number → record key, AR division number, Customer number → description, AR division number, Customer number → ERP code, Address line 1 → Address 1, Address line 2 → Address 2
Customer address	Customer address	12	Address line 1 → Address 1, Address line 2 → Address 2, City → City, Country name → Country, Customer name → Given name
Create Product	Product object	9	Item code → record key, Item code → name, Item description → description, Item product type → Item product type, Date created → Published date
Create Order	Order	34	Sales order number, AR division number → record key, Ship expire date → Closed date, Order date → Created date, Sales order number → Order number, AR division number → Number
Create Order Shipping Address	Order shipping address	12	Ship to address line 1 → Address 1, Ship to address line 2 → Address 2, Shipping city → City, Country name → Country, Shipping country code → Country code
Create Order Billing Address	Order billing address	12	Bill to address line 1 → Address 1, Bill to address line 2 → Address 2, Bill to city → City, Bill to country code → Country, Bill to country code → Country code
Create Order Line Item	Order line item	9	Unit price → Price, Quantity ordered → Quantity, Item code → Name, Item code → Title, the linked Salesforce record → product identifier

6. Verifying

The detail of this section is part of the operational skill. Whitelisted customers fetch it with dlake admin get_skill dlake-crmpro-shopify/erps/sage-100-us.

7. Where this sits

dlake-crmpro is the general operating surface — the CRMPro tools, the setup and transaction tables, field mapping, and the source view contract that applies to every destination. This page adds what the shipped Sage 100 (US) → Shopify templates set up. dlake-crmpro-shopify is the destination skill this page sits under: its own text is the authority for the Shopify conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the source data, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.

How to get started

Already a customer: the operational skill tells you how to connect, choose what to sync and run it. Fetch it with dlake admin get_skill dlake-crmpro-shopify/erps/sage-100-us, or ask support@commercient.com.
New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.