They can often be represented in Shopify, but the two platforms model products and option behavior differently. Each option, modifier, SKU, price adjustment, inventory rule, bundle, and personalization requirement should be classified as a native variant, metafield, line-item property, app, custom extension, or redesigned product flow.
Distinguish stock choices from customisation instructions
Consider an illustrative product with a size choice and optional engraving. Size may identify an independently stocked item, while the engraving text is an instruction for fulfilment. Treating both as the same kind of option can create unnecessary variants or lose information needed to complete the order.
Document how each BigCommerce choice affects SKU, stock, price, weight, images, and fulfilment. Then test the proposed Shopify representation through cart, checkout, order admin, and connected systems. If an app provides the customer interface, confirm that the data remains usable by the warehouse, returns process, and customer-service team.
What to check before deciding
- Classify each choice by its effect on stock and fulfilment.
- Test price adjustments and combinations with discounts.
- Verify that personalisation data reaches order and warehouse records.
- Check editing, refunds, and reorders for the chosen model.
