Connect BladePRO (i-fulfilment) to Rig

    Sync your BladePRO (i-fulfilment) warehouses, product variations, stock, orders, despatches, returns and purchase orders into Rig. Rig signs in to the BladePRO Public API with a username and password and reads from it.

    Before you start

    • You need a BladePRO username and password that can use the Public API.
    • The order, despatch, return and purchase order streams need read scopes on your account. Ask i-fulfilment to grant them if they are missing.

    Step 1: Check your API access

    1. Confirm the BladePRO user you will use can sign in to the Public API. BladePRO's API reference lists the production and sandbox hosts.
    2. If you are unsure which scopes the user has, ask i-fulfilment to confirm read access for orders, despatches, returns and purchase orders.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for BladePRO (i-fulfilment), open the card and click Connect.
    3. API base URL: Pre-filled with the production address https://public-api.bladepro.io. Leave it as it is, unless you are testing against the sandbox host.
    4. Username: Your BladePRO API username.
    5. Password: The password for that user.
    6. Order history window (days): Pre-filled with 90. This is how far back the first load reads orders, despatches and returns. Enter 0 for full history.
    7. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    8. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    BladePRO (i-fulfilment) lands in its own bladepro schema in your warehouse:

    • Warehouses: your fulfilment warehouses.
    • Product variations: the SKU master.
    • Stock: a point-in-time stock snapshot per active warehouse.
    • Goods out, despatched and returns: outbound orders, despatches and returns.
    • Purchase orders: inbound purchase orders.

    Goods out and despatched sync from the order history window forward by their order and despatch dates. Returns re-read a trailing period so late changes are caught.

    Good to know

    • BladePRO has no updated-since filter, so Rig walks order and despatch dates in windows. A first load with full history on a busy account can take a long time.
    • If your account lacks a read scope, Rig skips that stream with a warning and syncs the rest.
    • Stock is a snapshot from the latest sync, so keep history in the warehouse if you want stock over time.
    • To disconnect BladePRO (i-fulfilment), click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Track the order to despatch pipeline
    • Monitor stock by warehouse
    • Analyse returns

    More ideas for using BladePRO (i-fulfilment)

    BladePRO (i-fulfilment) documentation

    Was this guide helpful?