Source ERP · 23 of 24
CRMPro → Shopify — SYSPRO 7 and above: what the shipped templates set up
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/syspro-7-and-above". 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/syspro-7-and-above-shopify/.
CRMPro → Shopify — SYSPRO 7 and above: 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/syspro-7-and-above (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 product parent 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 those first; this page does not repeat them.
Where the catalogue and a live install disagree, trust the install and say so.
1. What the default catalogue delivers
Four template groups ship for SYSPRO 7 → Shopify.
| Group | Business outcome | Object | Source view |
|---|---|---|---|
| Customer | ERP customers become Shopify customers: the name is split into first, middle and last, the email and phone come across, and the ERP customer code travels with the record | Customer | new customer feed |
| Customer Address | Each ERP customer’s shipping address becomes the default address on the matching Shopify customer | Customer address | new customer address feed |
| Product object | ERP stock codes become Shopify products, with the ERP description as the title and body, the stock code as the Stock keeping unit, the price from the ERP price table and the on hand quantity summed across warehouses | Product object | new product feed |
| Product object update | Keeps an existing Shopify variant in step with the ERP: one leg pushes the on hand quantity when it differs from Shopify’s, the other pushes the selling price when it differs | Product quantity, Product price | product quantity update feed, product price update feed |
Note the split: creation and maintenance are different processes on different objects. Product creation happens once through Product object; everything afterwards is the two Product object update legs. A price change in the ERP does not flow through the create leg, because that leg never revisits a product it has already created.
2. The source data and the sync output
| View |
|---|
| new customer feed |
| new customer address feed |
| new product feed |
| product quantity update feed |
| product price update feed |
Run sequence in this set is 1 and 2 in the customer group, 1 in the product group, and 1 on both update legs — values that collide across groups, so set a coherent order yourself after import.
3. A worked create view
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-shopify/erps/syspro-7-and-above.
4. A worked update view
The mirror join, the value carrying record key and the integer cast are the three things dlake-crmpro-shopify warns about, and this is the view they are read from.
5. Where this sits
dlake-crmpro is the general operating surface, and 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/syspro-7-and-above, 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.
