Connect orders, inventory, shipping and routes and ask where the delays are and what will run out. Sherlok answers with the number and the decision to act in time.
until the best seller runs out, at the pace of the last 4 weeks.
Restocking takes 15 days. Placing the supplier order this week avoids the stockout.
Sources you connect
For an in-house ERP or WMS, connect the SQL database with a read-only user. Other sources come from the catalog. See all 1,500+ connectors
The order was late and the first person to know was the buyer.
The best seller runs out because nobody crossed the sales pace with the stock balance.
Every shipment is a spreadsheet, and comparing time and cost per carrier becomes a project.
Which orders were more than 3 days late this week?
Which carrier has the most delays this month?
Which products will run out in 2 weeks at the current sales pace?
How many deliveries missed the promised window, per route?
What is the average shipping cost per region?
Which paid orders haven't shipped yet?
of one carrier's shipments arrived late in October, versus 6% for the others.
Moving southern shipments to the second carrier cuts delays without raising the average cost.
Answers about orders, inventory, shipping and routes with data from the connected source, and closes with a decision.
The weekly summary with the agents' decisions, for whoever owns delivery.
Reads any source connected to the workspace when it helps explain the number.
Not yet: the agents for each area are in their final stage. Today, in logistics, Investigate does the work: you ask about orders, inventory and shipping and get the decision. When they're ready, they'll show up here.
Yes, through the database: connect SQL with a read-only user and allow the orders, inventory and shipping tables.
No. The connection is read-only. Sherlok points out what to do and your team acts.
Investigate queries the source at question time, so the answer uses the latest data the source provides.
Other areas