Shopify POS→Clover

Assess the Shopify POS source

Separate product/variant CSV, customer CSV and location inventory export; retain Shopify IDs and handles.

If Shopify ecommerce remains, match its existing products and decide the ongoing inventory owner before loading another catalog.

Keep an untouched original and a record of account, edition, location coverage and extraction time. The customer must provide full authorized access and be able to access their own data. Do not infer missing fields or access from a vendor family name.

Plan the Clover destination

Merchant inventory/customer workflows with approved write permissions; confirm item variants, modifiers and stock separately.

A modifier and a stock-bearing variation are different relationships. Third-party rewards and payment configuration are separate from merchant catalog records.

Inspect existing receiving records before choosing create, match or update behavior. An exported internal ID should remain in a reconciliation crosswalk unless the receiving specification explicitly accepts it.

Directional data decisions

A representative test for this direction

Use a product already sold online, two variant barcodes and stock at two Shopify locations. In the receiving Clover setup, also inspect an item with variants and modifiers plus a customer whose loyalty is held in an app. Use these illustrative examples to plan your project’s sample and agree expected results before a production import.

Write expected identities, grouping and quantities before the sample load. Compare returned records and rejected rows, approve exceptions and capture changes made after the stock snapshot. Test any proposed history or balance operations separately so an item import cannot silently create a second liability or stock movement.

What remains to be confirmed

• Confirm the selected customer/catalog matching behavior and location stock method for the receiving account.
• Confirm regional merchant permissions, variant/modifier mapping, contact writes and location stock operation; no general inbound connector is established.
• Confirm exact source/destination editions, authorized full access, included fields, existing destination records and retailer approval of history/balance treatment.
• No prior Sqquid test evidence was supplied. Run a representative controlled test and record actual results before executing this migration; do not publish an exercised-route or all-data guarantee.

This route remains under review. Request an assessment to establish the actual method and scope before booking. We confirm the exact edition pairing and supported fields before booking.

Official references

• Shopify product CSV workflows
• Shopify customer CSV requirements
• Shopify location inventory CSV
• Clover data model and relationships
• Clover application permissions
• Shopify guide: migrate from Clover

What the vendor documentation establishes

Shopify product CSV workflows: Products use a dedicated CSV workflow; contacts and multi-location quantities need separate receiving operations.

Shopify customer lists: Customer CSV is distinct from products; contact fields do not recreate orders or balances.

Shopify inventory CSV: Inventory is mapped to destination products and locations; establish a cutoff and inspect the destination export before updating.

Additional vendor boundaries

Clover data model: Items, variations/modifiers, stock and customer records have separate relationships; an approved field map and operation for the complete direction is still required.

Clover app permissions: Application permissions govern accessible records; a general merchant account does not demonstrate the required dataset access.