MILabs
Integrations

Order tracking portal for Katana stock and order records

How an order tracking portal reads order and stock records from Katana, what to confirm first, and where separate connections are needed.

Updated 2026-02-09

Order tracking portal with Katana

For a business that runs its stock and production in Katana, the portal's main job is to show buyers the same order picture the team already sees. Katana keeps the order and inventory records, so the portal reads its status from there rather than from a separate spreadsheet that drifts out of date. Small-batch manufacturers and food producers often find the harder task is agreeing which Katana states count as received, packed or dispatched. Those are decisions for the operations lead, and the build should record them before any customer sees a status. Freight updates, customer messages and carrier tracking sit outside Katana, so they need their own connections if the portal is to show them. Access depends on the plan and user permissions set for the account, so those should be confirmed early. Katana's API is the route for reading records into a portal, so check its current endpoints before design starts.

How it works

  1. Choose which Katana order and inventory records the portal shows, then connect the matching endpoints with permissions set for your account plan, so every order reads clearly.

  2. Set up a connection that reads order records from Katana, keeping write access out of the first version so the portal cannot change stock or orders.

  3. Map the stages the business uses in its own order process to plain labels such as received, packed, dispatched and delivered, and agree the mapping with the dispatch lead.

  4. Attach invoices and delivery notes to each matching order, using files from Katana's exports where the reporting view allows, and store them against the customer's login.

  5. Test the portal against a copy of recent orders, checking that each buyer sees only their own records before the page goes live.

good questions, straight answers

Frequently asked questions

Do I need a developer to connect an order tracking portal to Katana?
In most cases, yes. Katana's API exposes order and inventory records, but turning them into a secure customer-facing page needs someone who can build a small web app and handle logins. Operations staff can still define the stages, fields and customer views, and review the result. Whether the connection is written in code or built through an automation tool depends on the mapping and the permissions set for the account.
How does an order tracking portal stay in step with Katana?
It stays in step by reading Katana's records on a schedule or on request, so a status change in the account appears in the portal without anyone retyping it. The reading should be one-directional at first, which keeps the portal from altering stock or orders by mistake.
How do I know an order tracking portal works with Katana?
You know it works when a test order moves through each stage in Katana and the portal shows the same status, dates and documents. Use a few real orders, including one that changed after confirmation, to see how the portal handles awkward cases. Ask the dispatch lead to compare the two screens at each stage before buyers are invited in.
Can I start with a part of an order tracking portal on Katana?
Yes. A sensible first step is the status view for a single customer group, using only the stages the dispatch team already records. Dates, invoices and delivery notes can follow once that view is steady. Notifications, carrier links and reordering are best left until the team has seen how buyers use the page. Starting small lets the mapping to Katana be tested on a few orders before it carries the whole customer base.
How does MILabs test an order tracking portal against Katana?
MILabs tests the portal on a staging copy that uses recent order records from Katana, so the team can check statuses, dates and documents without touching live orders. Each stage in the mapping is compared with the matching record, and any mismatch is logged and resolved before launch. Customer views are checked to confirm that each login sees only its own orders. Results go to the operations lead, who signs off the mapping before buyers are invited in.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.