Your ERP setup through your assistant
If your shop is connected to an ERP (for example Fishbowl) and is on the Elevate plan, a connected assistant can work with the ERP part of Logistified much like you do in Settings → ERP. It can read and change the settings you can change there, decide how ERP parts link to your products, start a sync and see the work running in the background. It can also tell you what is wrong with the setup right now, and why an item shows the number it does. On a multi-store main store it can fix why orders from your other stores cannot be matched.
On this page
Section titled “On this page”- Who can use it
- What the assistant can see and change
- Asking for a health check
- What the assistant can fix, and what it hands on
- Asking why an item shows a number
- Orders from your other stores
- Safety: preview first, limits and the activity log
- What stays with support
Who can use it
Section titled “Who can use it”- Your shop needs an ERP connection (switched on or off) and the Elevate plan. If either is missing, the assistant does not see the ERP part at all. If the plan lapses, it loses access straight away.
- Reading needs any key; changing needs a key with write access. An assistant connected with a Read only key can check the setup and explain numbers, but sees none of the changes. Create a Read & write key when you want it to fix things (see API keys).
What the assistant can see and change
Section titled “What the assistant can see and change”- Settings. Everything you can change in Settings → ERP: the connection’s on/off switch, how ERP location groups map to your locations, which sales channels count as demand, lead-time and incoming-supply choices, vendors as suppliers, and the daily stock history (on or off). It also sees what the connector is allowed to read, and who can change each item: you, or Logistified support.
- Parts. Every ERP part with its link to one of your products, the products it could match, its vendors and lead times. It can link, unlink or ignore parts, one at a time or many at once.
- Syncs and background work. Every sync run with its result, and the work Logistified does after a change, such as rebuilding demand history or ingredient demand. It can start a sync and retry work that stopped after temporary errors.
- History. Every change made to the ERP setup, from Settings or from an assistant, with who made it.
Asking for a health check
Section titled “Asking for a health check”Ask the assistant something like “Is anything wrong with my ERP setup?”. It gets one report listing every current problem, most serious first. Each problem says how many items it affects (and, for large numbers, that the real count may be higher), shows a few examples, and explains in a sentence what it means. The assistant can then list every affected item if you want to go through them.
The report covers, among other things: a connection that is switched off or cannot be switched on yet, syncs that failed, have not run for a while or never ran, ERP location groups whose stock lands nowhere, parts that match several products or that sell but match none, demand history that is being rebuilt or stopped after errors, recipes (BOMs) the ingredient demand had to skip, quantities in units that cannot be converted, orders the wholesale checks left out, bought items still on the default lead time, lots without an expiry date, failing stock reads, vendors that could not become suppliers, a stock history that fails or is still catching up, and order lines from your other stores that could not be matched.
A sync that ran in the last day and a half is current. After that the report mentions it, and after three days it warns. A stock history that is still reading its past is reported as progress, not as a problem.
What the assistant can fix, and what it hands on
Section titled “What the assistant can fix, and what it hands on”Every problem comes with what to do about it, in one of three forms:
- Something the assistant can do now, such as mapping a location group, linking a part to the right product, retrying work that stopped after temporary errors, starting a sync, or matching an order line from another store to the right product. Changes are previewed first (see below).
- Something only Logistified support can do, such as approving an ERP table for the connector. The report says exactly what to ask for.
- Something to change in your ERP, such as giving an order a valid date or adding a unit conversion. These clear by themselves after the next sync.
Orders the wholesale checks leave out are explained, never “fixed” by loosening a check: the checks do what you set them to do.
Asking why an item shows a number
Section titled “Asking why an item shows a number”Ask “Why does this item show this demand?” or “Where does its lead time come from?”. The assistant gets an explanation in sections (demand, lead time, stock, lots, incoming, supplier, the linked ERP part, and any earlier variant whose sales history it took over). Each section says what it covers, where the number comes from, how fresh it is, and which setting or approval controls it. Stock and lots are the values last read from your ERP, with their time; the explanation never fetches them live.
Demand from ERP sales, from your other stores and from other external orders is stored as one number. When you need the split, the assistant can trace it from the individual order lines and confirm that the parts add up exactly to the stored total. For an item with very many orders this happens in several steps.
With a saved forecast view, the assistant can also show the item’s forecast under that view, clearly marked as covering only that view’s locations and settings.
Orders from your other stores
Section titled “Orders from your other stores”If this shop is the main store of a multi-store setup, orders from your other stores are copied in so their demand counts here. An order line that cannot be matched to one of your products waits in quarantine. The assistant can fix the cause for the orders that come in from now on:
- Match a product code. When another store sells an item under a SKU you do not use, or that matches more than one of your products, the assistant can say which of your products (or ERP items) that SKU means for that store. It can also list and remove these matches. Before you confirm, the preview shows how many lines in quarantine the match would resolve.
- Map a location. It can set which of your locations an order from another store’s location lands on.
- Match through your ERP. It can let unmatched lines from a store be matched through your ERP parts, when exactly one active part fits.
These changes apply to orders copied in from now on. Orders already copied in, and the lines already in quarantine, stay as they are until Logistified support copies that store’s orders in again (see What stays with support). Order sync, mirroring the other store’s locations and inter-store transfers stay in Settings → Multi-store: the assistant cannot switch them on or off.
Safety
Section titled “Safety”- Preview first. Every change is first run as a preview. It writes nothing and shows exactly what would happen, including any history rebuild it would start. Only when you confirm does the assistant apply it.
- Nothing changes behind your back. The assistant says what it last saw. If that changed in the meantime (for example because you saved in Settings), the change is refused and the assistant sees the current state, so it does not overwrite your work blindly. Repeating a change that already went through changes nothing.
- Limits. Changes that make Logistified recalculate demand history are limited per connection (three in a row, then one more every ten minutes), so an assistant cannot keep your shop busy. Changes you make in Settings are never limited.
- Activity log. Every change, from Settings or from an assistant, is recorded with who made it. The assistant can read that log too.
What stays with support
Section titled “What stays with support”Some things stay with Logistified support:
- connecting or disconnecting an ERP, and the connection key;
- which ERP tables the connector may read (the health report says what to ask for);
- copying in again the orders your other stores already sent, so that a new product match or location mapping also applies to them, and the demand history rebuild that follows.
See also
Section titled “See also”- What the assistant can read
- API keys: read and write access.
- Multi-store: order sync, quarantine and location mapping.