MILabs
Integrations

Custom development for Katana inventory and manufacturing records

Custom development for Katana businesses, with fixed-price builds that link stock, production and sales records to the tools your team already uses.

Updated 2026-03-17

Custom development with Katana

Katana keeps the stock, purchase, production and sales records for many small manufacturers, food producers and online sellers. Its standard screens cover most daily work, but some businesses reach a point where a reorder rule must follow their own supplier terms, a production cost needs a step that the built-in reports may not show, or a customer needs order status without a shared login. That is where custom development fits. MILabs, a Sydney agency, starts with the decision that slows the team down, then checks which Katana records it depends on against the vendor's API documentation. The build is scoped at a fixed price, tested on real account data, and handed over with upkeep inside the retainer. You own what is built. Businesses outside Sydney are served remotely.

How it works

  1. Name the decision your team repeats each week in Katana, such as approving a supplier order or pricing a production run.

  2. Map the Katana records that feed that decision, including stock, purchase orders, production jobs and sales, and confirm which fields your plan and user permissions expose.

  3. Agree a fixed-price scope that states the inputs, the output and the person who approves each action before anything is written back to Katana.

  4. Build the custom application or internal tool, connecting to Katana through its documented API so reads and approved updates stay in one place.

  5. Test the build against a copy of recent account data, including returns and partly completed production jobs.

  6. Hand over the working system with documentation, then keep it running and adjusted within your retainer as the product range changes.

good questions, straight answers

Frequently asked questions

How is custom development different from the other MILabs services for Katana?
The other services usually start from a general need, such as adopting AI tools, setting a strategy, automating a workflow or shaping a product idea. Custom development starts when a Katana business already knows the requirement that the existing setup cannot meet. The work is scoped at a fixed price for that requirement, then built as a system you own. Workflow automation can handle many routine handoffs, while custom development suits a bespoke application or a complex integration that needs its own logic.
What are the common mistakes with custom development and Katana?
A frequent mistake is building a custom tool before the team agrees on the decision it should support, which leaves the output unused. Another is assuming every record is open to an integration, when API access and visible fields depend on the Katana plan and the permissions set for each user. Teams also sometimes expect a forecast to account for sales outside Katana, though it only reflects the history the account holds. Confirm these points early so the fixed-price scope matches what the account can supply.
What does a Katana business need before custom development?
It helps to have a short list of recurring decisions, such as when to reorder a material, how to price a finished run or when to release a customer order. Each decision should be linked to the Katana records behind it, with a named person who approves the action. Someone should also be named to own upkeep.
Who is custom development for among Katana users?
It suits Katana users whose operation has outgrown the standard screens and reports. Small-batch manufacturers with unusual costing, food and beverage producers tracking ingredient lots in a particular way, and ecommerce brands with stock held in several places are typical examples. The common thread is a process the team repeats often and cannot yet handle cleanly in the account. If the need is a one-off report, a simpler setup may be enough.
Can custom development be done without a developer for Katana?
A finished custom system still needs developers, because the build calls Katana's documented API and must be tested before anyone relies on it. Your team can take part without writing code. Staff can describe the decision, supply sample exports, review test results and approve each automated action. Simple reporting needs may be met with the exports Katana allows from its reporting views, but any build that writes changes back to the account needs developer design, testing and handover.
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.