Purpose
Use these tables to understand where a value comes from and compare the same product variant, order or receipt quantity on both sides. Imports bring Shopify data into Optiply. Receipt-driven stock updates go in the opposite direction, from Optiply toward Shopify.
For app creation, permissions, connection checks and help with setup, use Connect Shopify to Optiply. This mapping guide is for reading values, not changing connection settings.
Before you start
Identify whether your connection uses the REST or GraphQL Shopify connector, which system supplies your product catalogue and whether supplier import is selected. Use a record you are authorized to view. For a receipt comparison, identify the variant and all receipts included in the same export batch; one batch can contain several receipts for a variant.
Keep app secrets, access tokens and other sensitive connection details out of screenshots and messages. Use the setup guide's support handoff when you need help confirming the connection or its schedule.
Steps
- Choose the value you want to check: product, sale, supplier product, composition or receipt quantity. Check the flow direction below before comparing it.
- Match the same variant in Shopify and Optiply. The parent product's identifier and the variant's identifier serve different purposes. For a sales-only connection, check the matching SKU in the system supplying products.
- Find the Optiply field in the tables. Use the source column for your connector version, including any stated conversion or matching rule.
- For receipts, compare the total quantity for the same variant in the selected batch. The export adds receipt quantities; it is not an absolute stock-level value. Do not create another receipt to test the mapping.
- If values differ, check the conditions under Limitations and follow Errors and recovery. Confirm the import or export job separately from the field comparison.
Flow direction and connection choices
| Flow | Direction | Choice or condition |
|---|---|---|
| Products and product changes | Shopify → Optiply | Variant-level import; a sales-only connection uses products from another source instead. |
| Product deletions | Shopify → Optiply | Full product comparison can disable missing products; deletion handling depends on the connection's job. |
| Product compositions | Shopify → Optiply | Optional and off unless selected; parent and component products must already be matched. |
| Suppliers and supplier products | Shopify → Optiply | Optional; check whether supplier import is selected for your connection. |
| Sales orders and lines | Shopify → Optiply | Closed, non-cancelled orders by default; a configured start date can restrict the eligible period. |
| Receipt-driven stock updates | Optiply → Shopify | Separate from incoming stock. Compare receipt quantities, not the product's absolute stock level. |
Fields and columns
Product
An Optiply product represents a Shopify variant. The Shopify product identifier becomes the article code; the variant identifier becomes the remote identifier.
| Optiply field | REST source | GraphQL source or meaning |
|---|---|---|
name | Product title plus variant title | Product title plus variant title; the placeholder Default Title is removed. |
skuCode | Variant sku | Variant sku; a missing value becomes empty. |
articleCode | Product id | Product legacyResourceId, matched with the variant's product reference. |
price | Variant price | Variant price. |
unlimitedStock | True when variant inventory_management is null, otherwise false | False for this import branch. |
stockLevel | Variant inventory_quantity | Variant inventoryQuantity; numeric whole-unit output. |
status | Product status | Active becomes enabled; archived or draft becomes disabled. New disabled products are not created. |
remoteId | Variant id | Variant legacyResourceId. |
eanCode | Variant barcode | Variant barcode; a missing value becomes empty. |
createdAtRemote | Product created_at | Product createdAt, converted to the expected date-time format. |
For unlimitedStock, REST uses the variant's inventory-management value: null becomes true. The GraphQL-capable import sets this field to false. The field names UnlimitedStock and remoteID can also appear in mapping references; the Optiply product fields above are unlimitedStock and remoteId. If the connection's half-stock option is selected, the imported stock quantity is divided by two and rounded before it is sent as a whole number. With the GraphQL-capable connector, half-stock and supplier import are off by default. Older REST-only connections can use different defaults; confirm both choices with support before comparing values.
Product composition
| Optiply field | Source and meaning |
|---|---|
composedProductId | Shopify parent-variant reference, matched to the corresponding Optiply product identifier. |
partProductId | Shopify component-variant reference, matched to the corresponding Optiply product identifier. |
partQuantity | The component quantity supplied for the composition. |
remoteId | The Shopify composition reference. |
Composition import is optional. Both product references must match before a row can be created. A new composition marks its parent as assembled; changes to the component quantity update the composition. Removing a composition in Shopify does not automatically delete it in Optiply or reset the parent's assembly setting. Ask support to review a removed composition before changing the assembly setup yourself.
Sell order
| Optiply field | REST source | GraphQL source |
|---|---|---|
totalValue | total_price | totalPriceSet.shopMoney.amount |
placed | processed_at | processedAt |
completed | closed_at | closedAt |
remoteId | Order id | Order legacyResourceId |
The remote order identifier is also written as RemoteId in older mapping references. The placed date comes from the processed date, not a separately named creation date. When a sales-order start date is configured, the processed calendar date must be strictly after it: orders processed on that date are excluded, even later that day.
Sell order line
| Optiply field | Source and meaning |
|---|---|
productId | Matched Optiply product identifier; also described as product_id or optiplyWebshopProductId in mapping references. |
quantity | Shopify line quantity. |
subtotalValue | REST line price, or GraphQL discountedUnitPriceSet.shopMoney.amount. |
The regular product-import route matches the Shopify variant identifier. Sales-only connections match the SKU against products supplied to Optiply by the other system. The mapped line price is sent as supplied; do not multiply it by quantity to interpret this field.
Supplier
| Optiply field | Source and meaning |
|---|---|
name | Shopify product vendor; distinct vendor names create suppliers. |
Shopify's Vendor value supplies the supplier name. If you need multiple supplier products for one product, agree the supplier-data source with support before changing the connection. Supplier import also controls the Shopify inventory-item cost mapping; it is not a switch for every supplier flow from other systems.
Supplier product
| Optiply field | Source and meaning |
|---|---|
name | The matched product name. |
productId | Matched Optiply product identifier, also described as product_id in mapping references. |
supplierId | Matched Optiply supplier identifier. |
skuCode | Inventory-item/product variant sku. |
eanCode | The matched product's barcode. |
price | Inventory-item cost, or GraphQL unitCost.amount. |
status | Inherited from the matched product; it is not always enabled. |
Supplier-product status follows the matched product's status, rather than a fixed enabled value. A null source cost becomes zero. A displayed zero therefore does not tell you whether Shopify supplied zero or no cost. Supplier import is not used by the sales-only or secondary-store product-sharing routes.
Receipt quantity
An Optiply Item Delivery supplies an additive receipt quantity, not an absolute Shopify stock balance. Match the same variant and compare the whole export batch, because several Item Deliveries can contribute to one quantity. Check the export job separately; do not create another receipt or resend an inventory update to test a difference.
| Value | Meaning in receipt-driven export |
|---|---|
Optiply receiptLines.quantity | Receipt quantity included in the export; quantities for the same variant are added together within the batch. |
| Product external variant reference | Matches the receipt's product to the Shopify variant. It is not the parent product's article code. |
| Add operation | The prepared quantity is an addition to stock, not a replacement stock balance. |
Shopify's inventory_item_id identifies an inventory item; it is not an extra Optiply receipt field. Do not look for it as an Optiply destination column or use it in place of the variant reference when comparing records.
Expected result
You can identify the source of each listed Optiply value, match the same variant or order, and explain any conversion that applies. For a receipt batch, you can compare the additive quantity for the same variant without confusing it with incoming stock or an absolute balance. Check the connection's job result separately to confirm processing.
Limitations
A connection's selected flows, connector version, schedule and custom mappings affect which values arrive. A field table is not a reason to enable an additional flow. Confirm the applicable schedule before interpreting a timestamp difference as a failed sync.
GraphQL products need variant records with valid variant and inventory-item identifiers. A parent product alone is not a substitute. Sales lines also need a matching Optiply product. Ordinary later sales-order changes, line changes, line deletions and added lines on an existing order are not imported as updates by this route; ask support to review cancellations or deletions rather than assuming an existing sale was removed.
Receipt-driven outbound stock updates and inbound Shopify stock are separate. Turning on outbound updates is not a fix for a missing incoming stock value. Do not resend a receipt or change stock to test a difference: that can create another stock movement.
Errors and recovery
- A product is missing: check the variant, its active status and its identifiers. For GraphQL, confirm that variant data exists; do not substitute the parent product identifier.
- An order or line is missing: check closed/cancelled status, the processed-date filter and the product match. For a sales-only connection, compare the exact SKU in both sources.
- A supplier cost is zero: compare the original cost with the matching inventory item. A null cost and a genuine zero can produce the same result.
- A composition differs: check both matched products and the component quantity. Ask support to review a removed composition or assembly setting.
- A receipt quantity differs: compare the same variant and the whole selected batch, then check the export job. Do not create a duplicate receipt or repeat an inventory update. Use the setup guide's support handoff if the difference remains.
For the wider connection choices, read the integration overview.