Salesforce
Custom integration — assessment requiredJoin CRM ownership with field execution.
Explore data & scopeAssess selected WooCommerce records alongside your field workflow. Plugins, custom statuses and guest checkout can materially change the mapping. No ready-made WooCommerce connector is verified.
Record ownership and direction are defined below. No universal two-way sync is implied.
Guest orders do not always provide a reusable customer identity.
Plugin-added statuses may have company-specific meanings.
Variable products need variation-level field mapping.
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 customer records | WooCommerce → SalesTOS | WooCommerce | Trade customer context | Assessment: registered and guest matching |
| Products and variations | WooCommerce → SalesTOS | WooCommerce | Catalogue reference | Assessment: variation and unit mapping |
| Order summaries | WooCommerce → SalesTOS | WooCommerce | Customer conversation context | Assessment: selected statuses and fields |
| Stock and refunds | No automatic exchange | WooCommerce | Store operations | Separate scope; not promised |
WooCommerce provides REST APIs. Review WordPress hosting, authentication, installed plugins and custom fields. A proposed API or event design must respect the store’s actual permissions and operational constraints.
An agreed set of wholesale customers and order summaries could be supplied to the field team. The representative records the next visit in SalesTOS while store staff manage fulfilment in WooCommerce.
A field activity does not automatically edit an online order, refund a payment or adjust inventory.
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Test plugin-specific responses, stable order IDs and duplicate event handling before rollout. A custom connector needs clear failed-run visibility and a correction owner.
Plugin-specific fields and behaviour require review; blanket compatibility is not promised.
Agree an identity rule using approved fields; names alone are insufficient.
Variation identifiers and units are candidates for mapping during assessment.
No. Inventory synchronisation is a separate transaction scope.
WooCommerce/WordPress versions and hosting; Relevant plugins and custom order states; Guest-customer and variation examples; Authorised API access and staging store. 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. A field activity does not automatically edit an online order, refund a payment or adjust inventory.
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 & scopeAssess commerce context for your trade sales team.
Explore data & scopeBring your business workflow and current setup. We’ll use them to assess the right data scope.