Rain POS→Shopify POS

Prepare the Rain POS source

Export products through Inventory > Products > Bulk Actions > Export. Use Customers > Customers > Options > Bulk Customer Actions > Download Customers for the customer CSV, rather than exporting a marketing list. Obtain store quantities through Inventory > Bulk or the Inventory report, recording location/status filters and the snapshot time. Separate available stock from reservations.

Keep an untouched extract, included-store list and source-to-destination identity crosswalk. Each retailer’s catalog, barcodes, orders and customer information are proprietary and unique; the field map is agreed with that retailer.

Load Shopify POS in separate steps

Build Shopify product CSVs first, then customer CSVs, then a location inventory file tied to the resulting variant identities. Inspect existing products and customer overwrite settings before loading. Keep Rain IDs in the reconciliation crosswalk; they are not Shopify IDs. Customer CSV does not recreate orders, passwords or historical spending.

Use Rain’s customer record download as the contact source. Inspect its actual columns before mapping addresses, consent and duplicate candidates into the destination customer template. The source customer ID belongs in the crosswalk unless the destination explicitly supports it; an email list or an account-balance report is not a substitute for contact records.

Illustrative mapping for this direction

These fictional rows describe acceptance checks, not an executed migration or a verbatim vendor template. Download the actual current templates for the engagement.

Where Shopify already hosts the retailer’s online catalog, match existing variants instead of creating a second listing. Reconcile Rain available/reserved stock to the agreed Shopify inventory state; the numbers are not interchangeable.

Keep complex records out of an ordinary stock file

Do not flatten serial numbers, repair/work orders, rental contracts, consignment commitments or reserved items into an ordinary quantity without an agreed outcome. Rain’s inventory reports document serial visibility/printing; that alone does not establish a full serial export and reload. The sold-serial SVP extract is not a complete in-stock serial register.

Agree a supported technical method, a reference archive or an explicit exclusion for each requested complex dataset. Customer contacts do not recreate gift-card liabilities, store credit, rewards, receipts or open orders. If any of those are required, establish their identity links and financial treatment separately before accepting that scope.

Acceptance before launch

Check every included store, barcode and sellable combination against the crosswalk. Reconcile created, matched, updated and rejected records; compare stock by store and record trading changes after the snapshot. Check a duplicate-contact candidate and a corrected-file retry for unintended duplicates or extra stock. The project lead and retailer agree exceptions, reversal steps and launch signoff. These project checks do not imply prior delivery evidence.

Vendor documentation and limits

• Rain bulk product and inventory operations distinguishes new products, updates, adding quantities and editing quantities, with separate location identifiers.
• Rain customer records and bulk templates establishes customer CSV download/upload independently of marketing lists.
• Rain spreadsheet rules explains header preservation, customer address format and blank-cell behavior.
• Rain inventory reports documents filtered quantity exports and the distinction between on-hand and reserved stock.
• Shopify product/item workflow
• Shopify customer workflow
• Shopify location inventory workflow