Shopify POS→Rain POS

Prepare the Shopify POS source

Export Shopify products/variants, customers and location inventory separately. Preserve existing online product identities and decide which system owns inventory if Shopify ecommerce remains.

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 Rain POS in separate steps

Use a fresh Add New Products template from Rain Inventory > Bulk for new records. Re-uploading it can create duplicates. Match existing Rain products first and use Edit Existing Products for updates. After catalog identities are established, Add New Inventory adds quantities/costs to existing products; Edit Existing Inventory is a different operation. Confirm destination location IDs and the required quantity change before uploading.

Rain’s customer module provides a blank upload template as well as a customer download. Keep its column structure. Rain documents one customer address column and says blank upload cells do not clear existing values; do not use blanks as a deletion strategy. Confirm how the actual receiving template matches an existing customer before a production load.

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.

If Shopify ecommerce remains, verify a linked online variant still points to the intended Rain sellable combination and assign the continuing stock owner. A continuing integration is separate from the migration.

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