Square preparation should begin by defining how the Target Store will use Square Catalog, locations, inventory, Customer Directory, Orders, payments context, fulfillment, Square Online, and connected applications. Square represents a Product family as a Catalog Item and its sellable units as Item Variations; modifiers, Categories, custom attributes, taxes, discounts, and locations remain separate relationships.
A useful preparation package records the action, owner, evidence, and ready condition for each major area. This prevents a source Product option from being misclassified as a Square modifier, a location-specific stock quantity from being reduced to one total, or historical payment evidence from being confused with current Square payment configuration.
Confirm the Square Operating Model and Location Scope
Define whether Square will support point-of-sale activity, Square Online, one or several physical locations, warehouses, services, delivery, pickup, shipping, or external fulfillment.
| Preparation area | Decision to record | Owner | Ready evidence |
|---|---|---|---|
| Square account structure | Merchant account, main location, additional locations, and business units | Commerce/operations owner | Location-purpose map |
| Selling channels | POS, Square Online, external marketplace, invoicing, or other channels | Channel owner | Channel and Order-source inventory |
| Inventory ownership | Square, ERP, WMS, supplier, or another stock authority | Inventory owner | System-of-record matrix |
| Customer ownership | Customer Directory, CRM, loyalty, marketing, or external account system | Customer owner | Customer-domain map |
| Fulfillment model | Pickup, delivery, shipping, warehouse, service, or external fulfillment | Operations owner | Fulfillment relationship summary |
| Square Online | Products, Categories, pages, routes, domains, and navigation in scope | Site owner | Square Online content and URL inventory |
The operating model is ready when every location and channel has a purpose, every inventory source has an owner, and Square Online requirements are separated from Catalog records.
Prepare Access, Source Archives, and Control Evidence
Collect:
- source administrator access and required Square Dashboard permissions;
- access to Catalog, Items, modifiers, Categories, locations, inventory, Customers, Orders, Square Online, and connected applications;
- dated exports or backups for Products, Customers, Orders, content, media, discounts, taxes, and custom data;
- location, inventory, and fulfillment reports;
- application exports and external-system documentation;
- external Product, variation, Customer, Order, and location identifiers;
- a source-change owner for catalog, Customer, Order, content, and stock updates during the migration window.
| Evidence item | Why it matters | Ready condition |
|---|---|---|
| Access record | Confirms required source and Square areas can be inspected | Responsible owners have the required permissions |
| Dated source archive | Preserves a recoverable reference state | Files open correctly and include export dates |
| Location inventory | Establishes the operational scope of quantities and Orders | Every source location has an intended Square or external destination |
| App inventory | Exposes records outside Square core | Every active application has a named owner |
| External-ID register | Protects reconciliation and synchronization | Keys are assigned to the correct Square object type |
| Change log | Captures updates after the reference archive | Catalog, Order, Customer, and inventory changes have accountable owners |
If a source system cannot provide an export, record the limitation and owner instead of assuming the relevant records are unimportant.
Prepare Catalog Items, Item Variations, Options, and Modifiers
Square Catalog separates Items, Item Variations, Item Options, modifiers, Categories, discounts, taxes, images, units, and custom attributes. Prepare representative source patterns that expose those distinctions.
Include:
- simple Products that will become one Item with one Item Variation;
- Products with size, color, style, or other variation dimensions;
- Item Variation SKU, barcode, price, unit, image, and stock relationships;
- reusable Item Options and inconsistent legacy variation names;
- list-based and text-based modifier requirements;
- Products with taxes, discounts, units of measure, or custom attributes;
- services, digital entitlements, subscriptions, bundles, or application-owned behavior;
- ERP, warehouse, marketplace, supplier, and accounting identifiers.
| Source behavior | Square preparation decision | Required evidence | Ready condition |
|---|---|---|---|
| Source Product has child SKUs | Define Item and Item Variation structure | Parent/child IDs, SKUs, prices, images, units, and stock | Every sellable child has one intended Item Variation |
| Variation values are standardized | Define reusable Item Options and values | Option vocabulary and combination examples | Equivalent variations use consistent option values |
| Buyer chooses an addition or preference | Define modifier list, modifier, or text modifier | Choice limits, prices, defaults, and Order-line examples | Modifiers are not treated as stock-bearing variations |
| Product uses descriptive custom data | Define Catalog custom attribute or external owner | Field purpose and consumer | Each field has a named continuing owner |
| Product behavior is app-owned | Identify continuing application or replacement | Related Items, Customers, and Orders | Required application data appears in the dependency register |
The Catalog area is ready when every major Product family has a defined Item, Item Variation, Item Option, modifier, tax, discount, Category, and identifier treatment where relevant.
Prepare Categories, Images, Taxes, Discounts, and Custom Attributes
Prepare Catalog relationships beyond Items and variations:
- Category hierarchy or Product grouping;
- images associated with Items, Item Variations, or Categories;
- taxes and Product tax assignments;
- discounts, pricing rules, and historical promotion context;
- measurement units and quantity precision;
- custom attribute definitions and values;
- source visibility or channel flags;
- Square Online Product and Category relationships.
| Catalog object | Owner | Evidence | Ready condition |
|---|---|---|---|
| Category | Merchandising owner | Category and Item membership list | Each Category has a current business purpose |
| Image | Content owner | File, role, sequence, and owning Item/variation/Category | Media relationships can be reconstructed |
| Tax | Finance owner | Tax names, percentages, inclusivity, and Item assignments | Historical values and current configuration are separated |
| Discount or pricing rule | Commercial owner | Rule, eligibility, dates, and affected Items | Active target rules are distinguished from historical Order outcomes |
| Unit | Catalog/operations owner | Unit name, precision, and applicable variations | Quantity meaning is documented |
| Custom attribute | Business/integration owner | Definition, object type, and consumer | The value is assigned to the correct Square Catalog object |
Do not reduce these objects to Product text. Their relationships can affect checkout, reporting, search, inventory, and external integrations.
Prepare Locations, Inventory Counts, and Stock Authority
Square inventory is calculated for Item Variations at locations. Inventory records can include current counts, physical counts, adjustments, transfers, and states such as in stock, sold, returned, received, or waste.
Prepare:
- every source warehouse, store, branch, supplier pool, or fulfillment location;
- the intended Square location for each source stock pool;
- Item Variation and location identifiers;
- current counts and the timestamp they represent;
- reserved, damaged, returned, in-transit, or other source states;
- external inventory authority and synchronization keys;
- opening physical counts and source-change ownership.
| Inventory case | Owner | Evidence | Ready condition |
|---|---|---|---|
| One location | Inventory owner | Item Variation count report | Every quantity maps to one Square location |
| Several locations | Operations owner | Variation-location matrix | Each source location has an approved destination |
| ERP/WMS-owned inventory | Integration owner | External IDs and synchronization example | Square opening values and future authority are documented |
| Source state has no direct target equivalent | Operations owner | State definition and affected examples | Consolidation, exclusion, or external ownership is recorded |
| Historical adjustments | Finance/operations owner | Adjustment and physical-count examples | Current opening count is separated from historical movement records |
The area is ready when every stock quantity has one Item Variation, one location, one timestamp, and one authoritative owner.
Prepare Customer Profiles, Groups, Segments, and External Identity
Square Customer profiles can contain contact details, company information, addresses, reference IDs, notes, groups, segments, marketing preferences, and custom attributes. Prepare identity records according to their actual business role.
Include:
- registered and guest buyers;
- duplicate email or phone examples;
- Customer groups and segment relationships;
- company or organization context;
- marketing preferences and consent evidence;
- loyalty, gift card, membership, or subscription relationships;
- CRM, ERP, marketplace, and accounting identifiers;
- Order relationships and historical addresses.
| Customer case | Owner | Evidence | Ready condition |
|---|---|---|---|
| Retail Customer | Customer operations | Contact, address, and Order examples | Identity and Order relationships are documented |
| Guest buyer | Customer operations | Order-level identity and addresses | Guest history is not converted into an unsupported permanent account assumption |
| Group or segment | Commercial/marketing owner | Group definition and representative Customers | Classification purpose and target owner are known |
| Loyalty or gift relationship | Application/finance owner | Account ID, balance/history, and Customer link | Program data is separated from the base Customer profile |
| External CRM Customer | Integration owner | CRM ID and matching rule | Durable cross-system identity is preserved |
Authentication, stored payment methods, loyalty ledgers, and specialized application profiles require separate owners. A Square Customer profile does not automatically reproduce those relationships.
Prepare Historical Orders, Payments, Fulfillment, and Returns
Select Orders that expose Item Variations, modifiers, custom line items, taxes, discounts, service charges, tips, Customer references, location, source, fulfillment, payments, refunds, and external IDs.
| Historical area | Required evidence | Ready condition |
|---|---|---|
| Purchased Items | Item/variation IDs, modifiers, quantities, and line prices | The purchased configuration is understandable |
| Adjustment context | Taxes, discounts, service charges, and tips | Historical totals can be explained |
| Customer and location | Customer ID, guest context, location, and Order source | Operational origin is documented |
| Payment and refund | Payment references, tenders, refunds, and dates | Historical finance context is separated from live payment configuration |
| Fulfillment | Pickup, shipment, delivery, tracking, and status | Past fulfillment remains understandable |
| External lineage | POS, marketplace, ERP, accounting, or support IDs | Reconciliation keys remain attached to the correct Order |
Historical Orders preserve past sales and returns. Current payment activation, devices, POS settings, shipping, delivery, pickup, taxes, staff permissions, and notification behavior remain separate Square configuration.
Prepare Square Online Content, Domains, Navigation, and URLs
When Square Online is in scope, prepare:
- Product and Category online visibility;
- Square Online pages, policy content, Blog or editorial content where applicable;
- navigation, footer links, campaign landing pages, and internal links;
- Product, Category, page, and campaign URLs;
- metadata, images, canonical relationships, and redirects;
- domain ownership and cutover dependencies;
- pickup, delivery, shipping, and location relationships shown online;
- embedded forms, widgets, scripts, and application content.
| Online area | Owner | Evidence | Ready condition |
|---|---|---|---|
| Product/Category presentation | Commerce/site owner | Visibility, content, images, and routes | Catalog and online presentation ownership are separated |
| Page or policy content | Editorial owner | Body, media, metadata, and source URL | Each content record has a destination |
| Navigation | Site owner | Menu tree and link destinations | Priority customer paths are documented |
| Domain and redirect | SEO/site owner | Source/destination URL ledger | Every priority route has an approved outcome |
| Fulfillment presentation | Operations owner | Location, pickup, delivery, and shipping examples | Online promises are connected to the intended locations |
Square Catalog data alone does not recreate Square Online page structure or navigation. Those records require separate evidence and owners.
Inventory Applications, APIs, and External Systems
Create a dependency register for every Square application, source extension, API, webhook, automation, marketplace, ERP, PIM, WMS, CRM, accounting, tax, shipping, loyalty, subscription, booking, delivery, analytics, and reporting system.
For each dependency, record:
- business purpose;
- Catalog Items, Item Variations, Customers, Orders, locations, inventory, or content affected;
- authoritative system and external IDs;
- export or API availability;
- configuration and credentials owner;
- continuing destination, replacement, or retirement decision;
- evidence required before the destination workflow is configured.
The register is ready when every active custom attribute, listing ID, loyalty value, stock key, or Order reference has a named owner and parent Square object.
Select Representative Migration Test Samples
| Sample | Preparation purpose |
|---|---|
| Simple Item with one variation | Establish the ordinary Catalog pattern |
| Item with several options and variations | Expose Item Option, SKU, price, image, and inventory relationships |
| Item with list and text modifiers | Expose buyer customization and Order-line evidence |
| Multi-location inventory variation | Expose variation-location mapping and stock authority |
| Customer with group and Orders | Expose profile, group, reference ID, and historical relationships |
| Complex Order | Expose modifiers, taxes, discounts, service charges, payment, refund, fulfillment, and location |
| Square Online priority route | Expose Catalog, content, domain, navigation, and redirect ownership |
| App-owned or external record | Expose the continuing system and stable Square identifiers |
For every sample, record the source ID, source URL where relevant, business reason, intended Square object, location, external keys, known exclusions, and responsible reviewer.
Complete the Square Readiness Gate
| Readiness question | Required evidence | Ready condition |
|---|---|---|
| Are access and source archives recoverable? | Access record and dated exports/backups | Required source records can be inspected independently of the live Store |
| Is the operating and location model defined? | Channel, location, inventory, and fulfillment map | Every location and channel has an owner |
| Are Catalog structures prepared? | Item/variation/option/modifier matrix | Every major Product pattern has an intended Square representation |
| Is inventory ownership prepared? | Variation-location and system-of-record matrix | Each quantity has a location, timestamp, and owner |
| Are Customers and Orders prepared? | Customer classification and historical Order packets | Identity and transaction context are understandable |
| Is Square Online prepared? | Content, navigation, domain, and URL ledger | Catalog and online presentation have separate owners |
| Are applications and external systems inventoried? | Dependency register | Every critical dependency has a continuing owner |
| Are representative migration samples selected? | Sample ledger | Catalog, location, Customer, Order, online, and integration complexity is covered |
| Are unresolved items controlled? | Decision log | Every open item has an owner and due date |
The preparation gate is complete when no critical Catalog Item, Item Variation, modifier, location, inventory, Customer, Order, Square Online, or integration decision depends on an undocumented assumption.
Conclusion
Square preparation should produce a location-aware commerce evidence package. Catalog Items must be connected to their Item Variations, Item Options, modifiers, Categories, taxes, discounts, and custom attributes. Inventory must remain attached to the correct variation and location, Customers and Orders must preserve their historical relationships, and Square Online or application records must have named owners.
When those decisions are documented before the representative migration test, the sample set can reflect the intended Square operating model without confusing historical commerce data with current POS, payment, fulfillment, or online configuration.
Common Questions
What should be prepared first for Square?
Start with the operating and location map. Define the Square locations, selling channels, inventory owner, fulfillment model, Customer systems, and Square Online scope before preparing individual records.
What is the difference between a Square Item and Item Variation?
The Item is the Product or service family, while Item Variations are the specific sellable units. SKU, inventory, price, option values, and other commercial data can belong to the variation.
When should a source choice become a Square modifier?
Use a modifier when the choice customizes an Item at purchase time without creating an independently stocked variation. Prepare list-based and text-based examples with their selection and price rules.
How should Square inventory be prepared?
Prepare a matrix connecting each Item Variation to its intended Square location, current count, timestamp, source state, and future system of record.
Should Square Online content be included in catalog preparation?
Catalog relationships and online presentation should be prepared together but owned separately. Pages, navigation, domains, redirects, and online fulfillment promises are not recreated by Item records alone.
When is Square preparation complete?
It is complete when access, Catalog objects, locations, inventory, Customers, Orders, Square Online, applications, samples, and unresolved decisions all have accountable owners and recoverable evidence.