Skip to main content

How to Set Up a ShipStation Custom Store Integration

A
Written by Airam Pabilonia
Updated over a week ago

Overview

Use the ShipStation Custom Store integration to let a third-party logistics provider (3PL) connect to Luminous without sharing sensitive ShipStation credentials. Instead of pushing orders into ShipStation via API, Luminous exposes a secure XML feed for ShipStation to pull orders, and a callback endpoint to receive shipment updates. This method ensures data security while supporting full fulfillment workflows.

When to Use This

Use the Custom Store integration when a 3PL refuses to share ShipStation API keys due to privacy or compliance concerns. This setup enables:

  • ShipStation to pull orders from Luminous

  • ShipStation to send shipment updates back to Luminous


Step-by-Step Setup

Step 1: Create a ShipStation Custom Store App Integration in Luminous

  1. Go to Luminous Admin (bottom left).

  2. Click Integrations.

  3. Go to System Settings > App Integration Accounts.

  4. Click + New App Account (top-right).

  5. Set App Type to ShipStation Custom Store.

  6. Add a Label (e.g., ShipStation - Custom Store).

  7. Click Save.

  8. Copy the generated:

    • Feed URL

    • Username

    • Password

You’ll use these credentials in ShipStation next.


Step 2: Connect the Store in ShipStation

  1. In ShipStation, go to Settings > Selling Channels > Store Setup.

  2. Click Connect a Store or Marketplace.

  3. Select Custom Store.

  4. Enter the credentials from Step 1:

    • URL = Feed URL from Luminous

    • Username = From Luminous

    • Password = From Luminous

  5. Map the "Awaiting Shipment" status to match Luminous.

  6. Click Save.


Step 3: Create a Fulfillment Channel in Luminous

  1. Go to Admin > Integrations > System Settings > Fulfillment Channels.

  2. Click + New Fulfillment Channel.

  3. Name it (e.g., ShipStation Custom Store).

  4. Set Push Orders Integration to the App Integration Account from Step 1.

  5. Click Save.


Step 4: Create a Sales Order in Luminous

  1. Go to Sales > Sales Orders.

  2. Click + New Sales Order.

  3. Select any Sales Channel.

  4. Add a Product.

  5. Click Save.


Step 5: Create a Fulfillment Order

  1. From the Sales Order, go to the Fulfillment Orders tab.

  2. Click + Create Fulfillment Order.

  3. Choose the Fulfillment Channel created in Step 3.

  4. Set the Ship Date.

  5. Leave Push to Integration unchecked.

  6. Click Save.

This prepares the order for ShipStation to pull.


Step 6: Pull the Order into ShipStation

  1. In ShipStation, go to the Custom Store.

  2. Click Actions > Import Orders.

The Luminous order will appear in ShipStation.


Step 7: Mark the Order as Shipped in ShipStation

  1. Open the order in ShipStation.

  2. Click Mark as Shipped.

Important: Ensure Notify Marketplace is checked — this triggers a shipment update back to Luminous.


Step 8: Confirm Shipment in Luminous

  1. In Luminous, go to Sales > Sales Orders.

  2. Open the order.

The Fulfillment Order status will be updated to Shipped, and shipment tracking will appear.


Concept Recap: Why Use the Custom Store?

  • Standard ShipStation integration requires API credentials — a security issue for 3PLs.

  • Custom Store integration flips the model:

    • Luminous exposes a read-only XML feed.

    • ShipStation pulls data on its schedule.

    • ShipStation posts shipments back to a controlled callback endpoint.

Think of it like this:

Method

Analogy

Access Level

API Integration

“Here’s my Netflix password.”

Full access – high risk

Custom Store

“Here’s a public menu and a callback number.”

Read-only – low risk


Common Questions

Can Luminous push orders directly into ShipStation in this setup?
No. With Custom Store, ShipStation must import the orders manually or on schedule.

Do shipment updates sync back to Luminous automatically?
Yes, if “Notify Marketplace” is enabled when marking an order as shipped.

Why can’t we use API credentials with a 3PL’s ShipStation account?
API credentials would expose all their clients' data — a compliance and security risk.

Did this answer your question?