The Luminous MCP server now supports full Purgatory management and Supplier SKU operations, allowing AI assistants and automation workflows to resolve unmapped orders and manage supplier-level SKU data without manually navigating the Luminous interface.
Overview
Previously, resolving Purgatory items and managing Supplier SKUs required manual action inside Luminous. With this expansion to the MCP server, these workflows can now be handled programmatically — through an AI assistant connected to Luminous or any automation built on the Luminous Scripting Platform. Use this when you want to automate SKU resolution, speed up Purgatory cleanup, or manage supplier product data at scale.
How It Works — Step by Step
Note: Ensure that Co-work is connected before doing the steps below.
Purgatory Management
1. List items currently in Purgatory
Ask your AI assistant to retrieve all orders currently stuck in Purgatory. The MCP will return a list of unrecognized SKUs along with the sales orders they are blocking.
Example prompt: "Show me everything currently in Purgatory."
2. Map an unmapped SKU to an existing Luminous SKU
Instruct the assistant to map a flagged SKU to an existing master SKU in Luminous. This is the equivalent of adding an Alternate SKU to a product — the order will be recognized and can proceed through fulfillment.
Example prompt: "Map SKU 'GOLFCLUB-BLU' in Purgatory to master SKU 'GC-001'."
3. Create a new SKU directly from a Purgatory item
If the flagged SKU represents a genuinely new product, the MCP can create a new master SKU in Luminous using the data from the Purgatory item.
Example prompt: "Create a new SKU in Luminous for the unrecognized item 'NEWPROD-XL' in Purgatory."
4. Ignore a SKU or pattern
For SKUs that do not require inventory tracking or fulfillment (e.g., gift cards, shipping line items, discounts), instruct the assistant to mark them as ignored. Ignored items will be automatically excluded from future Purgatory processing.
Example prompt: "Ignore all Purgatory items containing 'gift-card'."
5. Reprocess orders after resolution
Once SKUs are mapped, created, or ignored, instruct the assistant to reprocess the affected orders. This clears resolved items from Purgatory and allows the orders to continue through the fulfillment flow.
Example prompt: "Reprocess all orders in Purgatory that have been resolved."
Supplier SKU Management
1. View Supplier SKUs for a product
Retrieve the supplier-level SKU data associated with any master SKU in Luminous — including the supplier's own part number and the linked supplier record.
Example prompt: "Show me the supplier SKUs linked to master SKU 'GC-001'."
2. Add a Supplier SKU to an existing product
Link a supplier's part number to a Luminous master SKU. This is useful when a supplier uses a different identifier for the same product and you want that relationship recorded in Luminous.
Example prompt: "Add supplier SKU 'SUP-GOLF-BLU' from supplier 'Acme Co' to master SKU 'GC-001'."
3. Update an existing Supplier SKU
Modify a supplier's part number or update which supplier is linked to a given SKU mapping.
Example prompt: "Update the supplier SKU for 'GC-001' under 'Acme Co' to 'SUP-GC-2024'."
4. Remove a Supplier SKU
Delete a supplier SKU mapping that is no longer accurate or needed.
Example prompt: "Remove the supplier SKU 'SUP-GOLF-BLU' from master SKU 'GC-001'."
Key Features / Options
| Capability | What It Does |
|---|---|
| List Purgatory items | Returns all orders and SKUs currently flagged in Purgatory |
| Map to existing SKU | Adds the flagged SKU as an Alternate SKU on an existing master SKU |
| Create new SKU | Creates a new master SKU in Luminous from a Purgatory item |
| Ignore SKU / pattern | Marks a SKU or text pattern to be auto-excluded from Purgatory |
| Reprocess orders | Clears resolved items and moves orders back into the fulfillment flow |
| View Supplier SKUs | Retrieves supplier part numbers linked to a master SKU |
| Add Supplier SKU | Creates a new supplier-to-SKU mapping |
| Update Supplier SKU | Edits an existing supplier SKU record |
| Remove Supplier SKU | Deletes a supplier SKU mapping |
Tips and Best Practices
- Resolve before reprocessing. Always map, create, or ignore all flagged SKUs before triggering a reprocess. Reprocessing orders that still have unresolved items will not clear them from Purgatory.
- Use ignore for non-inventory line items. SKUs representing gift cards, discounts, shipping charges, or promotional items should be ignored rather than mapped — mapping them to a product SKU will cause incorrect inventory deductions.
- Supplier SKUs are not Alternate SKUs. A Supplier SKU records your supplier's part number for purchasing and receiving purposes. An Alternate SKU maps an external channel identifier to a master SKU for order processing. Do not use one in place of the other.
- Batch your Purgatory resolution. When multiple orders in Purgatory share the same unmapped SKU, mapping or creating that SKU once will resolve all of them — reprocess afterward to clear the full queue.
- Verify the master SKU exists before adding a Supplier SKU. If the master SKU hasn't been created in Luminous yet, create it first before attempting to link a supplier part number to it.
FAQs and Troubleshooting
Q: I asked the assistant to reprocess orders, but some items are still in Purgatory. Why?
A: There are likely additional unmapped SKUs on those orders that haven't been resolved yet. Ask the assistant to list remaining Purgatory items and address any that are still flagged before reprocessing again.
Q: I mapped a SKU in Purgatory, but the order still isn't moving. What should I check?
A: Confirm that the reprocess step was completed after mapping. Mapping alone updates the SKU record but does not automatically push the order back through fulfillment — reprocessing is required.
Q: Can I use the MCP to bulk-ignore an entire pattern (e.g., anything starting with "DISCOUNT-")?
A: Yes. You can specify a text pattern or regex-style string and the MCP will apply it as an ignore rule, the same way ignore patterns work in the Purgatory settings UI.
Q: Will adding a Supplier SKU via the MCP affect how purchase orders are created?
A: Yes. Supplier SKU data is used when generating purchase orders — the supplier's part number will appear on POs sent to that supplier, ensuring the right product identifier is communicated.
Q: Can the MCP create a new supplier record if one doesn't exist yet?
A: The MCP requires an existing supplier record in Luminous to link a Supplier SKU. If the supplier doesn't exist yet, create it in Luminous under Manage > Suppliers before using the MCP to add a Supplier SKU.
Additional Help
If you run into issues not covered here, or if an MCP action returns an unexpected result, reach out to the Luminous support team for assistance.