What is sent to the store?

Shopify: first name, last name, phone and an unsubscribe. WooCommerce: first name, last name and phone, because WooCommerce has no marketing consent field. Never a price, stock, a new customer or a yes to marketing.

What happens when the store and the CRM disagree?

For the catalogue the store wins. For a contact's details the last write wins, with an audit: the value we send replaces the store's, and the store's earlier value is kept beside it.

Can an AI assistant do this?

It can read: store_connections and store_catalog_status show the schedule, the last reading and write-back's state, and store_catalog_preview shows each option's price and stock. Turning the schedule or write-back on and sending to a store are a person's, on this screen.

Keep a store's products up to date, and send contact details back

Read a connected Shopify or WooCommerce catalogue on a schedule, with every option's price, compare-at price and stock. The store owns price and stock. Map the store's own fields, and send a contact's name, phone or unsubscribe back to the store only when you approve the list.

Steps

On Settings › Stores, open a Shopify or WooCommerce store, paste its read token and choose the currency. The token is sealed and never shown again.
Tick "Read changes from the store on a schedule" and choose every hour, every 6 hours or once a day. Each reading asks only for what changed since the last complete one, page by page, and waits when the store asks us to slow down.
The screen shows the last reading, what it created, updated or left alone, any conflicts, and the next reading. "Read changes now" and "Read everything again" run one at once.
For changes within a minute, add the store's product webhooks (Shopify: Product update and Inventory level update; WooCommerce: Product updated) with the same address and secret as your orders. A webhook only tells us to read again; the reading asks the store itself.
The store owns price, compare-at price, stock and availability: on its products they cannot be changed in CRM › Products, and the next reading also updates the name and description. A disclosure, a delivery note and a return policy you add stay yours. A product you built by hand with the same code is a conflict and is never overwritten.
Under the field mapping, "Find the store's own fields" asks the store which of its own fields exist (Shopify metafields and cart attributes, WooCommerce attributes and meta). Map a product field to a field on the product, and an order field to a field on the buyer's contact. An order fills a contact's field only when it is empty.
Write-back needs an operator to turn two-way sync on for the service. Check the token's write access (Shopify reports write_customers; for WooCommerce you confirm the key has Read/Write), turn write-back on, preview the list and send it. Only customers the store already has are updated, only the fields that differ, and the store's earlier value is kept in the log.
Every reading that wrote products can be undone from CRM › Products. Each write-back is in the audit log.

Questions

What is sent to the store?: Shopify: first name, last name, phone and an unsubscribe. WooCommerce: first name, last name and phone, because WooCommerce has no marketing consent field. Never a price, stock, a new customer or a yes to marketing.
What happens when the store and the CRM disagree?: For the catalogue the store wins. For a contact's details the last write wins, with an audit: the value we send replaces the store's, and the store's earlier value is kept beside it.
Can an AI assistant do this?: It can read: store_connections and store_catalog_status show the schedule, the last reading and write-back's state, and store_catalog_preview shows each option's price and stock. Turning the schedule or write-back on and sending to a store are a person's, on this screen.

Updated 2026-11-03 · llms-full.txt