Availability
The Shopify connection is available in Inklura Sync 0.8.12, distributed through your Inklura account. It supports simple and variable catalogues, creation in both directions, inventory, customers and default addresses. Configure compatible ordinary promotion codes separately.
Order imports are consultation copies. Real Shopify orders and payments remain untested on the demonstration store, which requires a subscription before accepting orders. Manage payments and fulfillment in Shopify.
Supported data
| Record | Behavior |
|---|---|
| Products and variants | Simple and variable products up to 100 variants: titles, descriptions, exact options, SKUs, primary barcode, prices and physical/virtual flags. Shopify imports and WooCommerce creation follow the configured directions; new exports always start as drafts. |
| Inventory | One explicitly selected Shopify location. Tracked quantities, concurrency checks and identified retries; untracked stock does not become zero. PrestaShop pair events continue through their own processing. |
| Customers | Names, email and phone of linked accounts; Shopify's default address maps to WooCommerce billing, with its own direction setting. No email-based merging, password transfer or automatic invitation. |
| Tags, images and collections | Tags follow the catalogue direction. Optional additive imports of Shopify images and collections as WooCommerce categories retain local media and categories. A separate option copies native photos on initial Shopify creation, up to 20 public JPEG, PNG or WebP images; existing mapped galleries are retained. |
| Orders and history | Shopify → WooCommerce consultation copies with linked lines/customers and tax checks. Optional fulfillment, tracking, refund summaries and transaction states. No second payment, refund or stock movement. |
WooCommerce relays products and customers to the PrestaShop pair under that pair's settings. This version has no standalone Shopify ↔ PrestaShop connector. Shopify orders remain in their consultation workflow.
Connect Shopify
- In Shopify's Dev Dashboard, prepare and install the app on the intended store. Client-credentials authentication requires the app and store to belong to the same organization; another organization requires an existing offline Admin API token. This version has no public OAuth installation flow.
- Authorize only the chosen features: catalogue and inventory, location reading, customers when enabled, and orders when imported. Shopify must also permit access to customer data.
read_products, write_products, read_inventory, write_inventory, read_locations, read_customers, write_customers, read_orders. - In WooCommerce → Inklura Sync → Shopify, save the exact STORE.myshopify.com domain and private credentials in Disabled mode. An empty secret field preserves its value; never publish credentials.
- Select Verify connection, choose the location, then directions and options. Currency and tax-inclusive/exclusive price entry must match WooCommerce; tax rates are not guessed.
- Configure webhooks from the same screen using API version 2026-10. Use the receiver shown by the Shopify screen if needed: it is separate from the PrestaShop webhook. Start in Audit and inspect the queue before Live mode.
- Schedule the worker every minute using the archive's operations guide. The existing tick command processes both connections; WP-Cron alone depends on visits. New-record creation and publication of imports remain separate choices.
Promotion codes
Compatible ordinary codes can be enabled with read_discounts, plus write_discounts for both directions: percentage, fixed-cart or fixed-item amounts, all customers/products, with no quota, stacking or additional conditions. Incompatible rules are suspended rather than approximated. Consumable quotas are not cloned into independent coupons.
Verify exchanges
- Create a draft test product, export its WooCommerce ID and check variants, prices and inventory in Shopify. Then test an edit from Shopify.
- Verify a test customer and default address in both directions without invitation email or use of a real customer's account.
- Check the Shopify queue and worker result, then the PrestaShop pair queue when it relays those records. Receiving a delivery does not prove a native write succeeded.
Limits and troubleshooting
- Concurrent edits or ambiguous identities require review. Do not clear mappings to force a match.
- Once records are mapped, changing the store or location requires an explicit migration. Disabling retains history and queues.
- Gift-card products, subscriptions, bundles, wildcard variants, mixed tax flags, protected downloads and structures beyond supported bounds require specific handling. Features do not silently truncate oversized data.
- No WooCommerce order export to Shopify or fulfillment actions. Payments and refunds remain on their source platform. Asynchronous stock does not atomically reserve the last item across checkouts.