A practical retail guide
Rain POS Shopify integration: connect or migrate?
Keep Rain and Shopify connected, or replace Rain with Shopify POS. The data plan depends on which change you need.
Rain POS advertises a Shopify integration. Connecting the two can let you keep Rain at the counter while using Shopify online. Replacing Rain with Shopify POS is a different project: it requires a one-time migration and a decision about Rain-only records and workflows.
Start with Rain’s current feature listing and confirm account eligibility, fees and the supported connection with Rain. This guide helps you plan the questions and data checks. It does not offer an ongoing integration service as part of the POS data migration fee.
Decide whether to connect or migrate
| Your intended change | Work to plan | Next step |
|---|---|---|
| Keep Rain as POS and use Shopify for ecommerce | Set up an ongoing connection with defined data ownership | Confirm the vendor-supported integration and test its behavior |
| Replace Rain with Shopify POS | Transfer agreed retail records and replace or retain service workflows | Review Rain POS to Shopify POS migration |
| Keep both temporarily during a transition | Define which system owns each dataset at every stage | Plan the connection and the final migration as separate operations |
The general migration versus integration guide explains why a successful import does not establish continuing synchronization.
What Rain’s setup guidance describes
Rain’s Shopify Integration Setup article, dated 11 July 2025, describes an initial product/customer connection followed by ongoing rules that make Rain the place for product and category edits. It also identifies limitations around refunds, locations and specialist retail records. The article contains beta-era wording. Confirm current behavior rather than treating every historical limit as a present platform rule.
Use this review matrix when discussing the connection with Rain. It lists checks to confirm, not a claim that every row is supported in your account.
| Data or operation | Ownership to agree | Test before relying on it |
|---|---|---|
| Products, variants and identifiers | Where product edits should be made after the initial connection | Change one intended field and inspect both records |
| Categories and collections | How the source hierarchy maps to Shopify organization | Check similar category names and nested groups |
| Inventory and locations | Which system controls stock and how locations are represented | Test a store sale, web sale and stock adjustment |
| Customers | How profiles are initially matched and later updated | Check a new customer and a corrected existing contact |
| Orders and refunds | Where fulfillment, cancellations and refunds must be performed | Confirm a complete order and the refund types you use |
| Rentals, repairs, classes, serials and liabilities | Supported connection, separate workflow or exclusion | Test the actual service record with the vendor before launch |
Prepare an existing Shopify catalog
If products already exist in both systems, compare identifiers and variant grouping before enabling another process that creates items. Similar names do not prove that two records represent the same sellable variant. Keep a mapping of the source identity and receiving identity, and agree how duplicate candidates will be handled.
In a fictional example, Rain has a blue shirt with two sizes, but Shopify has one listing with a different SKU on the larger size. Resolve that mismatch before the first connection. Otherwise a later sync could leave the intended product unmatched or create a duplicate.
Retain a baseline of the existing catalog and stock. Check whether an older connection remains active and have its owner coordinate any disconnection. Two independent processes updating the same inventory need an explicit ownership plan.
Troubleshoot with a specific record
For a missing product, inspect its identifiers, variant structure, intended selling availability and connection eligibility. For a stock difference, compare the item, store, stock state and timing of the last relevant sale or adjustment. For a customer mismatch, inspect the matching key without copying private contact data into an ordinary support message.
Ask the integration owner to trace the exact operation and receiving result. Do not repeatedly reload a full catalog as a substitute for diagnosing one unmatched item. Record retries and any correction so stock is not added or overwritten unintentionally.
If the goal is to leave Rain
A connection does not recreate rentals, repairs, open orders or customer liabilities in Shopify POS. List those commitments separately and agree a supported destination, archive or exclusion. Our Rain migration route covers the retail data questions for that change.
Check my migration if you are replacing Rain. If you are keeping Rain, use the vendor’s integration setup and support path to confirm the current connection.
Move with a clear plan.
Retail data migration for $2,999, with scope confirmed before booking.
Check my migration