Nightshift for Retail
Ask your commerce data anything. Your team and your agents.
Orders, inventory, pricing, and customers live in dozens of systems. Connect them once and Nightshift gives your merchandising, supply, and support teams and their agents warehouse-grade reads across all of it, with no warehouse to stand up and customer PII masked before it leaves. Agents draft refunds, fraud flags, and ticket updates back into Nightshift for a human to approve, and nothing they write ever touches checkout or payments.
One catalog, three agents
Each agent gets its own slice.
Merchandising agent
Pricing, stock, and trends across stores. No customer PII.
Support agent
Order lookups with email and phone hashed. Drafts refunds for your team to approve, never against payments.
Supply agent
Stock levels and supplier lead times, region by region.
Cross-source root cause
Find the margin leak, down to the SKU.
An agent connects Nightshift over MCP and attributes a 2.7-point gross-margin drop across Shopify, SAP, Salesforce, and the warehouse, down to the SKU and cause. No single system holds this answer: the catalog composes all four into one governed query.
| SKUShopify | Discount depthSalesforce | Landed costSAP | Margin ΔWarehouse |
|---|---|---|---|
| SKU-4021 | 28% | +6% | -0.9 pt |
| SKU-8830 | 15% | +3% | -0.7 pt |
| SKU-1174 | 9% | +11% | -0.5 pt |
| SKU-6650 | 22% | +2% | -0.4 pt |
| SKU-3390 | 12% | +4% | -0.2 pt |
The boundary
Reads cross. Writes land in Nightshift, never in checkout.
An agent reads commerce, CRM, and inventory through the catalog, and writes its work, a drafted refund, a fraud flag, a ticket update, into Nightshift’s own tables, where your team approves it before anything executes. Nothing an agent writes touches checkout or the payment system until a person signs off.
Customer PII
Enough to help. Not enough to leak.
A support agent needs the order, not the shopper. Contact and payment fields are hashed or dropped in the view, so they never reach the agent or its model.
What agents do
Agents on commerce data, not customers.
Help the shopper
A support agent that looks up orders with email, phone, and address masked, and drafts the refund or ticket update into Nightshift for your team to approve, never against checkout or payments.
Tune the assortment
Read pricing, stock, and trends across stores to suggest merchandising, with no customer PII in scope.
Watch the supply
Read inventory and supplier lead times region by region to flag a stockout before it happens.
Omnichannel
Every channel, one governed catalog.
Web, stores, marketplace, app, and the call center all land in one governed view. Agents read the whole picture, with customer PII masked the same way no matter where the data came from.
Governance in plain SQL
Mask the customer, grant read.
A governed view scopes an agent to its store region and hashes email, phone, and address. Grant the agent read on the view, and it is the only data the agent can reach.
- Scope rows and columns with a governed view
- Hash or drop contact and payment fields
- Agents write to governed Nightshift tables, never to checkout or payments
-- orders_safe: NA orders, customer contact hashedcreate view orders_safe asselect order_id, sku, amount, store_region,hmac(email, :pii_key) as email_token, -- keyed hash: joinable, not reversiblehmac(phone, :pii_key) as phone_tokenfrom orderswhere store_region = 'NA'; -- address and card not selected
Questions the team asks
What store ops wants to know.
- Will an agent leak customer data?
- Contact fields are hashed or dropped in a governed view, so a support agent reads the order without the shopper behind it.
- Can agents change prices or issue refunds?
- An agent can draft a refund, a price change, or a fraud flag, and it lands in a governed Nightshift table where your team approves it. Nothing executes against checkout, pricing, or payments until a person signs off, so the agent does the work and control stays with you.
- Does this touch our checkout?
- No. Nightshift serves a governed read of commerce, CRM, and inventory data. Your storefront and checkout are untouched.
Put an agent on your commerce data.
Start free, connect your store or warehouse, and watch governed reads reach your agent in minutes, with customer PII masked from the first request.
Want to look first? Take the product tour