Commerce topics with an operational point of view
The content is researched from primary documentation and written independently. Industry playbooks are labelled as such and never presented as unsupported client experience.
Migration & replatforming
Migrate Salesforce Commerce Cloud to Shopify
An SFCC to Shopify migration is not a data export but the deliberate replacement of cartridges, jobs, OCAPI or SCAPI flows, price books and accumulated campaign logic. The safe route inventories every extension, assigns it to standard, app, integration or retirement, and migrates catalogue, SEO and operations in testable waves.
Open playbookReplace Oracle ATG with Shopify in controlled stages
With Oracle ATG, the risk lies in custom business logic rather than product import. Repositories, droplets, pipelines and batch processes must first be sorted by business value. Shopify takes standard commerce, while the few stable differentiating processes are remodelled through apps or middleware.
Open playbookMove AEM Commerce experiences to Shopify
With AEM, the first decision is whether the CMS stays or is replaced with the commerce platform. If AEM remains, Shopify becomes the commerce core and AEM supplies selected content. If AEM goes, components, content fragments, assets, approvals and URLs form a migration of their own.
Open playbookMigrate a custom commerce platform to Shopify
A custom platform has no standard migration template. The safe route starts with observed processes, real data and code paths. Every capability is assigned to Shopify standard, an app, an integration, a custom extension or retirement before data, URLs and cutover are planned.
Open playbookMigrate stores and point-of-sale data to Shopify POS
A POS migration succeeds when store processes and inventory movements are decided before hardware. Locations, register roles, payments, gift cards, returns, tax and offline behaviour need realistic tests. The online store is only one side of the same inventory and customer view.
Open playbookMigrate from Global-e to Shopify Markets
Moving from Global-e to Shopify Markets starts with a market comparison rather than a country list. Assortment, pricing, currency, tax, duties, payment, shipping, domain and returns must be confirmed per market before a controlled market-by-market rollout is possible.
Open playbookMove from headless back to a Shopify theme
Headless-to-headed makes sense when the additional frontend operation no longer creates measurable value. The migration inventories storefront features, CMS content, preview, analytics, SEO and deployments, then maps only what is genuinely needed into the theme. The goal is lower system load, not a visual step backwards.
Open playbookMagento to Shopify: the technical migration guide
A technical Magento migration starts with websites, stores, store views, attribute sets, customer groups, price rules and extensions. Those structures are not copied blindly; they are redistributed across Shopify Markets, catalogues, metafields, apps and integrations. Data rehearsal, redirect testing and order reconciliation decide launch readiness.
Open playbook
Commerce integration
Shopify Microsoft Dynamics GP integration
GP owns products, pricing, inventory and financial documents; Shopify owns storefront, cart and checkout. The integration must handle older web services, partner solutions and a possible later ERP migration. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Oracle ERP integration
Oracle owns items, procurement, inventory and financial documents; Shopify owns selling and customer interaction. Oracle REST APIs, business events and asynchronous imports need to be combined by object and volume. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Acumatica integration
Acumatica owns ERP master data, warehousing and documents; Shopify owns the commerce experience and checkout. Contract-based REST endpoints and custom fields need version-stable documentation. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Manhattan Active Omni integration
Shopify captures orders; Manhattan orchestrates inventory, routing, fulfilment, cancellation and returns. The central question is when order ownership and the fulfilment promise move from Shopify to the OMS. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify IBM Sterling OMS integration
Shopify owns checkout and customer view; Sterling owns orchestration, promise and fulfilment across locations. Sterling APIs and event flows must be decoupled from Shopify order and fulfilment states. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Kibo Commerce integration
Shopify can own storefront and checkout while Kibo handles order management, routing and fulfilment. The boundary between Kibo commerce capabilities and Shopify must be deliberately reduced before integration. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Salesforce Order Management integration
Shopify captures the order; Salesforce OMS owns orchestration, service view and fulfilment processes. Customer, order and fulfilment identities need stable correlation between Shopify and Salesforce. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify NewStore integration
Shopify owns online commerce; NewStore can own mobile retail operations, omnichannel orders and the associate experience. Customer, inventory and order views must stay consistent across channels despite separate interfaces. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Pimberly integration
Pimberly owns product information, attributes and media; Shopify owns commerce-specific pricing, inventory and selling. Channel rules and product workflows need translation into a stable Shopify metafield model. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Syndigo integration
Syndigo owns syndicated product content and data quality; Shopify owns the direct sales channel. Retailer-specific syndication rules must not overload the Shopify channel with unnecessary data. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify STORIS integration
STORIS owns furniture retail, orders, inventory and delivery; Shopify owns digital product discovery and checkout. Configuration, delivery windows, deposits and store stock require domain-specific mapping. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Island Pacific integration
Island Pacific owns retail merchandising, inventory and store processes; Shopify owns storefront and online checkout. Style-colour-size structures and store availability must map to Shopify products, variants and locations. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbookShopify Contentstack integration
Contentstack owns editorial content and approvals; Shopify owns products, pricing, inventory, cart and checkout. Content references, preview and publishing must fit the storefront architecture without moving product truth into the CMS. A dependable integration defines the source, direction, event, retry, conflict rule and business reconciliation for every object before the first connector is configured.
Open playbook
AI & applications
Enterprise AI applications built for real operations
An enterprise AI application is dependable when the model, data access, permissions, evaluation set, cost and human escalation are designed together. The product value does not come from the first prompt but from reliable decisions across real edge cases and operations that make failures visible.
Open playbookInternal AI tools without shadow IT
An internal AI tool pays off when it removes a recurring bottleneck using approved data, explicit roles and measurable quality limits. It fails when a quick interface quietly becomes business-critical without an owner, support model or controlled change process.
Open playbookBuild business applications around Shopify
A Shopify-connected application makes sense when a business process goes beyond themes and standard apps while Shopify still owns catalogue, customers or orders. The application should extend the commerce core rather than duplicate it, using documented APIs, webhooks and stable IDs.
Open playbookCustom software or SaaS: a defensible decision
SaaS wins when the process is largely standard and speed matters more than differentiation. Custom software wins when stable, business-critical logic creates the advantage and a team exists to operate and evolve it. The usual middle ground is a standard platform with a small custom extension.
Open playbookAudit AI-built code before production
A security audit for AI-built code examines the resulting attack surface rather than how the code was produced. Authentication, authorisation, tenant isolation, secret handling, input validation, dependencies, logging and secure deployment matter. Prompting replaces neither threat modelling nor reproducible tests.
Open playbookProduction-readiness check for AI applications
Production readiness means an AI application does more than produce good answers: it responds predictably to outages, model changes, misuse and ambiguous cases. That requires an evaluation set, safe tool boundaries, cost and latency budgets, fallbacks, monitoring and a clear human escalation path.
Open playbook
Conversion & operations
Use conversion benchmarks without fooling yourself
A universal conversion benchmark is rarely a useful target. Comparison becomes reliable only when device, market, channel, new or returning customer, product price, availability and measurement definition match. The most useful benchmark is therefore your own cohort before and after a named change.
Open playbookOptimise product pages without merely adding elements
A strong product page answers purchase questions in the order doubts arise: does it fit, is it available, what do delivery and returns cost, which variant is right and why is the offer credible? Optimisation therefore means prioritising, not stacking more modules above the add-to-cart.
Open playbookShopify and Sage: integration guide
Every Shopify Sage integration starts by identifying the exact Sage product and edition. Products under the same brand differ materially in APIs, data model and operations. Only then can systems of record, objects, direction, frequency, tax logic, failures and reconciliation be defined.
Open playbook
Platform decision
Shopify vs Salesforce Commerce Cloud
Shopify fits when a hosted platform, short release cycles and a deliberately limited custom layer matter most. Salesforce Commerce Cloud fits when an enterprise is deeply embedded in Salesforce processes and can carry the additional platform and implementation complexity. The operating model matters more than the longer feature list.
Open playbookShopify vs Adobe Commerce
Shopify fits when platform operations, scaling and rapid releases should be standardised. Adobe Commerce fits when deep custom logic, complex B2B and full application-code control are strategically necessary and a permanent operating team exists. Both can support enterprise commerce with fundamentally different responsibility models.
Open playbook
Industry playbook
Shopify for media and entertainment: industry playbook
Drops, rights, bundles, digital and physical products and high peaks require explicit release and inventory logic. A dependable Shopify setup therefore starts with the industry's purchase and service process rather than a generic theme choice. This playbook provides practical guidance; it is not evidence of NICCOS client work in this industry.
Open playbookShopify for toys and collectibles: industry playbook
Pre-orders, age information, editions, bundles and scarce inventory need transparent rules. A dependable Shopify setup therefore starts with the industry's purchase and service process rather than a generic theme choice. This playbook provides practical guidance; it is not evidence of NICCOS client work in this industry.
Open playbookShopify for books and publishing: industry playbook
ISBNs, formats, publication dates, authors, series and direct reader relationships shape the data model. A dependable Shopify setup therefore starts with the industry's purchase and service process rather than a generic theme choice. This playbook provides practical guidance; it is not evidence of NICCOS client work in this industry.
Open playbook
