Before connecting an online store

• Use an administrator account in POS and your online store. Your POS address and product images must be reachable over HTTPS. Check Scheduler status before expecting automatic work.
• Keep catalog and stock changes in POS: they publish to the channel. Online orders flow back to POS; ordinary counter sales change stock but are not published as new online orders.

Connect Shopify

1. Create an app in the Shopify Dev Dashboard for the same organisation as the shop. Create and release a version, then install it on that shop. Copy its Client ID and Client Secret from the app settings.
2. Grant the integration scopes: write_products, write_inventory, read_locations, write_locations, read_publications, write_publications, write_customers, read_orders and write_merchant_managed_fulfillment_orders. Enable the required protected customer-data access for imported customer details.
3. In POS Sales channels, add Shopify, name the connection and enter the permanent myshopify.com domain, Client ID, Client Secret and supported API version shown by the connection settings.
4. Choose product, customer and order sync options, the payment method used to record paid imported orders, and whether to publish products online. Save and Test connection, refresh locations and map them before Sync now.
5. Check a sample product online. POS sends titles, prices, barcodes, variants, MRP as compare-at price, brand as Vendor and category information. Only the primary image is published; do not expect a complete gallery or separate variant images.

Connect WooCommerce

1. On the WooCommerce site, enable stock management and use readable permalinks instead of Plain. In WooCommerce → Settings → Advanced → REST API, add a key for an appropriate user with Read/Write permission. Save the Consumer Key and Consumer Secret.
2. Add WooCommerce in POS. Enter the HTTPS site root, not a REST API path, and paste the key and secret. Let POS generate the webhook secret or enter your own secure value. Set sync and payment recording options, then save and test.
3. If webhook registration failed, use WooCommerce Advanced → Webhooks to create active hooks for order.created, order.updated, order.deleted, customer.created and customer.updated. Use the callback URL shown by POS and the same secret.

Map stores, stock and order allocations

1. Map each online location to a POS store. Choose Location for individual stock, Aggregate for combined stock or Disabled to exclude it. Check the Inventory, Orders and Active switches separately.
2. Set allocation priority and safety stock. Lower priority numbers are considered first. The published quantity is on hand minus reservations and safety stock, never below zero.
3. Test connection checks access; Sync now queues synchronisation work. Review connection health and task results afterwards. Fix credentials, unmapped products or locations before retrying.
4. If a remote product was deleted, review its mapping and use Sync now to recreate it when intended. Disconnecting in POS does not delete the online shop. Provider outages leave local transactions intact.

Channel identity, health and recovery

• Each Shopify or WooCommerce shop has a separate connection. Give every product and variant a unique SKU before onboarding; saved mappings become the permanent identity after matching.
• Customers can move both ways through signed webhooks. POS owns product and stock changes; deleting a product archives it on Shopify or moves it to WooCommerce Trash. Shopify receives POS-managed category collections and the primary image; merchant-created collections stay separate.
• WooCommerce combines enabled POS stores into one core stock pool. Shopify can use individual locations or an aggregate location. Stock sent is an absolute available quantity, never a delta.
• Test connection checks credentials, locations and webhook registration. Sync now queues a full reconciliation. Pending work waits for the scheduler; failures need the displayed cause corrected. Provider outages retry with increasing delay without undoing local sales.
• For Shopify access errors, confirm the app is released and installed on the exact shop and approve changed scopes; protected customer data needs customer/order and name, address, email and phone access. For WooCommerce, check HTTPS, non-Plain permalinks, Read/Write keys, stock management and matching webhook URL/secret.
• Use Sync now to repair intentionally missing remote catalog records after checking mappings. Do not delete pending work to make the dashboard appear clear. Keep client secrets, consumer secrets and signing secrets out of screenshots.