Tool Overview: LaunchPad v1

What is Fluent LaunchPad?

• Using Postman’s advanced features:
  • Pre-request and test scripts (JavaScript before and after each request).
  • Control of execution order (decide which request runs next).
  • Reading responses and storing values (IDs, tokens, etc.) for later steps.
• Turning the collection into a “Smart Postman collection” that can:
  • Orchestrate complex flows.
  • Reuse logic across folders/requests.
  • Automate large parts of the setup instead of relying on manual edits.

Postman, Collection Runner and Automation

LaunchPad Account Setup

Folder Structure

• LaunchPad 0 – Dynamic Authentication
  • Entry point for every run.
  • Checks what file you’re uploading (retailers, locations, categories, etc.).
  • Performs dynamic authentication (log in as the right user).
  • Routes the workflow: e.g. “This is a locations file → run Launchpad 2 next.”
• LaunchPad 1 – Retailer Creation & Account Initialization
  • Handles:
    • Creating retailers via batch REST APIs.
    • Initializing the account with the right roles and users.

• LaunchPad 2 – Locations and Networks
  • Ingest locations and networks from a file.
  • Ensure required workflows exist if the entity is orchestrated.
• LaunchPad 3 – Categories and Products
• LaunchPad 4 – Global Inventory
• LaunchPad 5 – Fulfillment & Order Management Configuration
  • Focused on attaching workflows/config for fulfillment options and order management.

GraphQL vs REST Batch API

• For each retailer in the CSV
  • Create a job.
  • Add a batch to create that retailer.
  • Poll the “get batch” endpoint until the status is complete (asynchronous processing).
• Account initialization occurs only after all retailers in the file are created.

• A Store Assistant role (for later use).
• A Super Admin role with “god-mode” permissions.
• A new Super User account that will become the main setup user.

Super User Initialization

• Updates the retailer admin user:
  • Assigns the Super Admin role at retailer level, so that user can administer that retailer.
  • Assigns an “orchestration admin” role to give access to the orchestration modeler in the console UI.
• Updates the Rubix user for each retailer:
  • For every retailer, there is an internal Rubix user (used by orchestration workflows to call APIs).
  • Launchpad gives that user the GraphQL permissions it needs, so workflows can execute their API calls.
• Applies retailer-level settings:
  • Activates Rubix for standard and wave orchestration.
  • Configures pack lists and settings needed for Global Inventory.
• Creates helper entities for:
  • Reject location - A pseudo-location where unfulfillable fulfillments can be parked (this is not a real store, just a logical “sink”).
  • Demo carrier - A generic carrier (instead of a real DHL/UPS record). This is used in training workflows for Ship to Store, Home Delivery, etc.

• Created.
• Wired into orchestration.
• Accessible via console with the right admin users.
• Equipped with a basic carrier and failover (reject) location.

Recap

• What LaunchPad is for
  It takes you from an empty account to a working retail setup (retailers, locations, products, inventory, workflows) with minimal manual work.
• How it works (Postman + data files)
  You feed LaunchPad data files (CSV/JSON) containing retailers, locations, products, etc.
  Using Postman’s Collection Runner (or Newman on the CLI), it runs the same API flow for each row, turning hours of copy/paste into a few minutes of automated setup.
• LaunchPad folder steps (0–5)
  • LP 0 – Figures out what kind of file you provided and logs in as the right user.
  • LP 1 – Creates retailers in bulk via REST batch API and initializes the account (roles, users).
  • LP 2–4 – Load locations, networks, categories, products, and global inventory.
  • LP 5 – Wires up fulfillment and order management configuration.
• Super User pattern
  Because the default admin starts with no GraphQL permissions (and role caching used to be slow), LaunchPad:
  • Uses the default admin only briefly to create roles and a Super User.
  • Gives the Super User full permissions before first login (so cache is correct from the start).
  • Then, as the Super User, it:
    • Updates retailer admins (Super Admin + orchestration access).
    • Grants the internal Rubix users the GraphQL permissions needed for workflows.
    • Applies key retailer settings (Rubix activation, pack list/Global Inventory config).
    • Creates helper entities like the reject location and demo carrier.
• End state
  After LaunchPad runs, each retailer is:
  • Created and fully wired into orchestration
  • Usable in the console by the right admins
  • Ready for training/demo scenarios with a basic carrier and a safe “reject” location