One stock figure, shared by the shop and the warehouse.

CubeERP and Shopify

Orders in, stock and pricing out, fulfilment and tracking back - so the website sells what you actually have.

Selling online from a stock figure maintained separately is a slow-motion problem: overselling, cancellations, apologetic emails and a customer who does not come back. CubeERP holds one stock figure and publishes it to Shopify, receives orders directly into the sales order process, and pushes fulfilment and tracking back when the parcel leaves. Trade and retail can run on different pricing without maintaining two catalogues.

What moves

Exactly what is synced, and which way

Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.

  • Into CubeERP

    Orders and customers

    Web orders land as sales orders with customer, addresses, payment status and shipping method, ready to pick like any other order.

  • Out of CubeERP

    Stock levels

    Free stock published continuously, by location where you fulfil from more than one, so the shop cannot sell what is already allocated.

  • Out of CubeERP

    Products and pricing

    Product data, images, variants and prices maintained in CubeERP and published, so there is one catalogue rather than two.

  • Out of CubeERP

    Fulfilment and tracking

    Despatch pushes fulfilment status and the carrier tracking number back, triggering Shopify’s own notification to the customer.

How it behaves

The detail that decides whether it is actually useful

  • Near real-time stock

    Levels update as orders are taken and goods are received, rather than on an hourly file that is wrong for fifty-nine minutes.

  • Retail and trade pricing

    Separate price lists for retail and trade customers, including logged-in account pricing, driven from the same CubeERP pricing engine.

  • Multi-location fulfilment

    Publish availability per location and route each order to the site that should fulfil it, including drop shipping where appropriate.

  • Returns handled once

    Web returns arrive as returns against the original order, inspected and credited through the same process as any other channel.

Setting it up

Three steps, done during implementation

  1. 1

    Install the connection from your Shopify admin and authorise it - standard app authorisation, revocable at any time.

  2. 2

    Decide what is mastered where: usually stock and price in CubeERP, content and imagery in Shopify.

  3. 3

    Match existing SKUs before going live. Mismatched product codes are the single most common cause of a painful e-commerce integration.

Questions

What people ask about this one

  • Within seconds of the movement in normal operation. It is event-driven rather than a scheduled file, which is the difference between overselling occasionally and overselling regularly.

  • Yes - multiple stores, including different territories or brands, against one CubeERP instance with their own pricing and stock allocation rules.

  • Codes, stock and price in CubeERP; descriptions, imagery and content in Shopify where the marketing team already works. That split causes the fewest arguments.

  • POS orders arrive the same way as online orders and deplete the stock location you nominate, so a physical shop and the warehouse share one stock figure.

  • Supported. Items can be published as available to order with a promise date driven by inbound purchase orders rather than by optimism.

Shopify

Check the Shopify detail before you commit

Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.