Salesforce
Custom integration — assessment requiredJoin CRM ownership with field execution.
Explore data & scopeShopify store data and field sales serve different workflows. Evaluate a selective feed of eligible customer, product and order context. This is an assessment service, not an installable SalesTOS Shopify app.
Record ownership and direction are defined below. No universal two-way sync is implied.
Consumer checkout records may not belong in a trade customer list.
Variants need stable identifiers for field catalogue mapping.
Online order status must remain distinct from a field order request.
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Selected customers | Shopify → SalesTOS | Shopify | Eligible trade customer context | Assessment: purpose and authorised customer access |
| Products and variants | Shopify → SalesTOS | Shopify | Field catalogue reference | Assessment: variant IDs and selected fields |
| Selected order context | Shopify → SalesTOS | Shopify | Office and field coordination | Assessment: store and order scope |
| Refunds and fulfilment | No automatic exchange | Shopify | Commerce operations | Not included in proposed read scope |
Shopify documents the Admin GraphQL API. Review application access, authorised data scopes and the specific store before selecting a refresh or event design. API availability is not evidence of an existing SalesTOS app.
A store identifies customers eligible for a trade sales programme. Their agreed reference details and selected order context could support field visits, while online checkout and fulfilment remain in Shopify.
No automatic payment capture, refund, inventory adjustment or fulfilment update is promised.
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Define event deduplication if events are chosen, refresh cut-offs and customer-access boundaries. These controls belong to the proposed implementation and must be tested.
No verified installable Shopify connector is offered here.
No. Define the eligible customer segment and business purpose first.
Not under the proposed context feed. Stock changes require separate transaction design.
Yes, subject to current provider interfaces, permissions and a tested custom implementation.
Store and proposed business use; Authorised application access and data permissions; Customer-selection and variant examples; Order status rules and a test approach. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. No automatic payment capture, refund, inventory adjustment or fulfilment update is promised.
No matching questions. Clear your search or discuss your requirements with us.
Join CRM ownership with field execution.
Explore data & scopeTurn selected CRM records into purposeful field follow-up.
Explore data & scopeMake store-to-field data fit your WordPress setup.
Explore data & scopeBring your business workflow and current setup. We’ll use them to assess the right data scope.