# Kabaido, full content

> Kabaido is the AI-native industrial operations platform built around the engineering of your industry. This file carries the why, what and how of every product, area and part, and the full text of the Kabaido blog and documentation; the page map with one line descriptions is /llms.txt.

# Products

## Sales Engineer

URL: https://kabaido.ai/sales-engineer

Why: Technical requests arrive as emails and drawings, and the systems behind the sale cannot read them.
What: Sales Engineer reads the request, matches your catalogue, prices it on real costs and drafts the reply.
How: Connect Gmail or Microsoft 365; every draft goes to an internal address for review until you decide otherwise.

## Design Engineer

URL: https://kabaido.ai/design-engineer

Why: A custom enquiry needs a drawing and a price, and the CAD system was never built to quote.
What: Design Engineer configures the part, draws it, prices it on your real costs and puts it on a quote.
How: Each design module holds its own parameters, geometry, rules and price formula, so anyone in sales can drive it.

## Route

URL: https://kabaido.ai/route

Why: Customers plan production around a delivery date, so the date and the proof must hold.
What: Consignments, runs, loading and proof of delivery, from the confirmed order to the customer's door.
How: Every package move is a scanned trace event, and each delivery's cost is booked to its job.

## Source

URL: https://kabaido.ai/source

Why: A price is only as good as the cost behind it and the date you can commit to.
What: Suppliers, price lists, requests for quotation, purchase orders, goods in and invoice matching, beside your sales orders.
How: One request goes to many suppliers, the answers come back comparable and the winner becomes a purchase order.

## Stock

URL: https://kabaido.ai/stock

Why: An availability answer given while quoting is only worth giving if the quantity behind it is true.
What: Locations, transfers, stocktakes and reorder points over one ledger that every movement is written to.
How: Every balance is derived from the ledger, so each change carries a reason, a person and a time.

## Service Centre

URL: https://kabaido.ai/service-centre

Why: Work on a customer's own property is hard to trace, price fairly and cost by the job.
What: Service Centre registers each item, moves it through your stations and prices it on what was found.
How: Service models, rules and a scan at every station handover drive the price, the cost and the trail.

## Machinist

URL: https://kabaido.ai/machinist

Why: A job's real time and cost often stays at the machine, out of sight of the quote.
What: Machinist puts a screen at each machine, with a schedule, a trace and a cost model over them.
How: Jobs arrive from quotes, every scan at a machine is timed, and the minutes come back as cost.

## Wizard

URL: https://kabaido.ai/wizard

Why: The right product depends on the job, and the charts that decide it rarely reach the person choosing.
What: A deterministic selector that turns the application into a specification and ranks your own catalogue against it.
How: Each wizard compiles published manufacturer charts, sourced and dated, and answers the same way every time.

## Inspect

URL: https://kabaido.ai/inspect

Why: A first meeting spent learning what a manufacturer makes is a meeting not spent on what they need.
What: An evidenced map of UK manufacturers that says who to approach, what to lead with and what to ask.
How: Public sources become engineering profiles, your offering map ranks them, and every debrief sharpens your private view.

## Commerce

URL: https://kabaido.ai/commerce

Why: Customers ring to ask where an order is, when a tool is due back and what a quote said.
What: A branded sign in where your customers see their own quotes, orders, items and documents, plus an optional built website.
How: An access code per customer record, a policy per table they may read and none anywhere else.

# Platform areas

## The AI interface

URL: https://kabaido.ai/platform/ai

Why: Requests arrive as emails, POs and questions, and each needs the catalogue, the price and the engineering behind it.
What: One input for the whole workspace: paste a request, a purchase order or a question and get a cited answer.
How: The products you switch on decide what it can do; every chat stays under Recents in the menu.

## Quotes

URL: https://kabaido.ai/platform/quotes

Why: When quotes live in inboxes and spreadsheets, what is out, won or expiring is hard to see.
What: Every quote to a customer in one list, with the count and value at each stage.
How: Draft from a request or by hand, send the PDF with its portal link and track each answer.

## Orders

URL: https://kabaido.ai/platform/orders

Why: Once a quote is won, the order, the purchase, the job and the delivery often live in separate systems.
What: One Orders area for every direction of work, with a view for each product that adds one.
How: Accepting a quote raises the order at its quoted prices, and any later price change needs a reason.

## One record for every customer you sell to

URL: https://kabaido.ai/platform/customers

Why: Terms, contacts and order history sit in separate systems, so every reply starts with a search.
What: One record per customer: contacts, terms, addresses, special prices, quotes, orders and service items.
How: Import a CSV, add the fields your trade needs and ask the AI about any customer.

## Suppliers, price lists and requests

URL: https://kabaido.ai/platform/suppliers

Why: Buying well needs every supplier's terms and prices in one place, next to what you sell.
What: Suppliers, their contacts, their price lists and the requests for quotation sent to them.
How: Price lists import and match to your products; requests go out and answers come back comparable.

## The catalogue every quote is matched against

URL: https://kabaido.ai/platform/catalogue

Why: Product data lives in supplier files and spreadsheets, so matching a request means reading them by hand.
What: One catalogue of products described by schemas, filtered by their attributes and priced by rules.
How: Import CSV, XLSX or REST feeds, map them to a schema and the AI matches requests against them.

## Lines, locations and the ledger

URL: https://kabaido.ai/platform/stock

Why: Promises made at the quote need a quantity that is true wherever the stock sits.
What: Stock lines, locations, the movement ledger and the reorder list, in one area.
How: Every product writes movements through one writer, and each balance is summed from them.

## Servicing: the work, the registry and the rules

URL: https://kabaido.ai/platform/servicing

Why: A service workshop needs one place for every item, its station, its rules and its cost.
What: Servicing holds the day's work, every registered item, the service models, the rules and the costing.
How: Every view reads the same items and scans, so the registry, the rules and the costs agree.

## The workbench every design module runs in

URL: https://kabaido.ai/platform/design

Why: Made to order parts are quoted from drawings by hand, one enquiry at a time.
What: One workbench where a design module turns parameters into a model, a drawing and a price.
How: Set the parameters; the engine checks them, redraws the part and prices it from your own rates.

## The Wizard workbench

URL: https://kabaido.ai/platform/wizard

Why: Choosing the right blade or coating takes charts most buyers never see.
What: One workbench per wizard: run it, read the specification, see where it runs.
How: Each wizard installs with a preset and answers from its own sourced charts, with no model call.

## The shop, machines, operators, schedule and costs

URL: https://kabaido.ai/platform/machinist

Why: A machine shop needs its machines, people, schedule and job costs in one place.
What: The Machinist area holds each machine module's screens, plus machines, operators, schedule and costs across them.
How: Each machine module brings its own screens; machines, operators, schedule and costs span every one of them.

## Deliveries, runs and vehicles

URL: https://kabaido.ai/platform/route

Why: A promised delivery date is only useful if the day, the van and the proof all hold.
What: The consignments, runs, loading, vehicles and couriers that take a confirmed order to the door.
How: Deliveries come from orders, runs sequence the stops and every scan writes a trace event.

## The Inspect workbench

URL: https://kabaido.ai/platform/inspect

Why: Territory knowledge lives in a few heads, so the best prospects wait for the right person.
What: Seven views over one region: the map, lists, a visit run, companies, campaigns, your offering, profiles.
How: Every view reads the same evidenced profiles, ranked against your offering map and sharpened by debriefs.

## Customers online and your website

URL: https://kabaido.ai/platform/commerce

Why: The answers your customers ring for already sit in your workspace.
What: Customers online shows your sign in and who uses it; Website runs the trade site once one is connected.
How: An access code per customer record, your own address or domain and site orders landing as platform orders.

# Platform parts

## Specials and quantity breaks

URL: https://kabaido.ai/platform/pricing

Why: A price is only trusted when everyone can see how it was reached.
What: Discounts, special prices and quantity breaks set per customer, product, category or service, applied on every quote line.
How: A rule or a special sits against a product, category, schema, design module or service, and the most specific wins.

## Costing

URL: https://kabaido.ai/platform/costing

Why: A margin is only real when the cost behind it is measured, not assumed.
What: Costs held against products, stock, machines, operators, service steps and delivery runs, each from a real figure.
How: Work is timed where it happens and costed at your rates; a missing rate shows as a gap.

## Customer context

URL: https://kabaido.ai/platform/customer-context

Why: The right answer depends on who is asking and what they bought before.
What: Custom fields, patterns and history on every customer, fed to the AI only when you pin that customer.
How: Pinning a customer adds their counts, dates and fields, never a price or another customer's rows.

## Monitoring

URL: https://kabaido.ai/platform/monitoring

Why: Nobody can watch every quote, order and stock line all day.
What: Watchers set against an area that check on a schedule and act when something changes.
How: Each monitor checks every fifteen minutes, hourly or daily, then notifies the team or calls a webhook.

## Traceability

URL: https://kabaido.ai/platform/traceability

Why: When a customer asks where their item is, the answer should take one scan.
What: One Kabaido code on any item, batch, package or job, scanned and followed through the platform and the workshop.
How: Each scan writes an event with its station and the minutes since the last scan onto the trail.

## Integrations

URL: https://kabaido.ai/platform/integrations

Why: The platform has to fit the systems a business already runs, not replace them overnight.
What: Connections tailored per product, custom REST connections, signed webhooks, a REST API and an MCP server.
How: An admin connects each one in Settings, and API keys scope every call to one organisation.

## Roles

URL: https://kabaido.ai/platform/roles

Why: People should see the work they do, and a station should never show a price.
What: Five ranked roles plus operator, and job templates that set a person's role, areas and stations in one pick.
How: The ranked role decides what the database lets them change; the areas only narrow what their menu shows.

## Presets

URL: https://kabaido.ai/platform/presets

Why: A new workspace should start knowing the trade, not as a blank form.
What: Ready made setup for a trade, applied at onboarding or later, with schemas, design modules, wizards and service models.
How: Installing adds what the preset carries and asks before switching a product on; it creates no sample products.

## Customer facing

URL: https://kabaido.ai/platform/customer-facing

Why: Customers want to check a quote or an order without waiting for someone to reply.
What: Your own customers on a branded surface of the same platform, brought by Commerce, reading only their own rows.
How: A customer signs in with an access code, as a separate principal, never as one of your members.

## Activity

URL: https://kabaido.ai/platform/activity

Why: The team should hear about the moments that matter without watching every screen.
What: Every action recorded, and the notifications your team and your customers receive, each tuned per kind.
How: Each kind has a setting for the app and for email, which you or each person can change.

## Documents

URL: https://kabaido.ai/platform/documents

Why: The documents a customer receives are the business in their hands, so they must be right.
What: Quotes, orders, dockets, labels, purchase orders and delivery notes, generated from the record and branded as yours.
How: Each PDF renders from the live record with your logo, brand colour and footer, in your document language.

# Blog

## When the buyer asks an AI instead of a search engine

URL: https://kabaido.ai/blogs/when-the-buyer-asks-an-ai-instead-of-a-search-engine
Published: 2026-08-16 (updated 2026-09-24). Category: Method notes.

Industrial buyers are starting to ask assistants, not search boxes. What that changes for a supplier's website, what it does not, and what we did to ours.

Buyers who once typed bandsaw blade suppliers into a search box are starting to ask an assistant the whole question: which blade cuts 60mm 304 stainless bar, and who sells one?

The assistant answers in prose and cites a handful of pages. There is no page two. Either an answer engine can read, extract and cite your page, or you are not in the conversation.

## What actually changes

Less than the noise suggests. Google's own documentation says its AI features build on the established SEO fundamentals, and that a page needs nothing beyond being indexed and eligible for a snippet.

What shifts is the unit. A search engine ranks whole pages; an answer engine quotes passages. A section that answers one question in plain sentences, with its numbers in a table, gives an engine something to lift and attribute. One long unbroken claim gives it nothing to hold.

Figure: Two routes to the same buyer. The ranked list rewards being tenth or better; the synthesised answer rewards being extractable and citable at all.

## Structure is now legibility

Structured data used to be a garnish for rich results. For a machine reader it is closer to a contract:

- Organization says who is speaking.
- Product, with real offers, says what is sold and at what price.
- FAQPage says which questions the page answers.
- BreadcrumbList says where the page sits.

Add the boring hygiene: one canonical URL per page, an honest sitemap and hreflang that tells the truth about which languages exist.

## The polite conventions are young

llms.txt is newer and less proven: a proposed map of a site for AI systems at a well known URL, with an optional full text companion. There is no public evidence yet that any major engine reads it.

We publish both anyway. The cost is an afternoon, the file is honest whether or not anyone reads it, and our robots file names and welcomes the crawlers that do. This is a bet on a convention, not a measured channel.

## The same discipline as quoting

Industrial suppliers are well placed here, because it is the discipline their trade already runs on. An answer engine choosing what to cite does what a buyer's engineer does with a datasheet: it looks for concrete figures, stated sources and claims that stay inside their evidence.

The load table with its reference, the price with its currency, the roadmap item marked as a roadmap item: those are pages a machine can safely repeat. Puffery is not just unpersuasive now. It is unquotable.

### What we did to this site

- Structured data on every page, resolved to one Organization node.
- Product nodes on product pages, and the real plan prices as offers on the pricing page.
- FAQ markup that mirrors the visible questions.
- Canonicals, hreflang and the sitemap in agreement.
- A robots.txt that names and welcomes the AI crawlers.
- llms.txt as the map, and llms-full.txt carrying the blog and the docs in full, this post included.

Sources:
- Google Search Central: AI features and your website (https://developers.google.com/search/docs/appearance/ai-features)
- The llms.txt proposal (https://llmstxt.org/)
- This site's own llms.txt (/llms.txt)

## How to specify an industrial machine knife

URL: https://kabaido.ai/blogs/how-to-specify-an-industrial-machine-knife
Published: 2026-08-16. Category: Inside the work.

A machine knife order is three dimensions, a steel, a hardness and an edge. Most enquiries carry four of the six. Here is the full specification.

Industrial machine knives, the guillotine blades, slitters, granulator knives and shear blades that cut everything from coil steel to plastic regrind, are ordered by the thousand across UK industry and almost never by part number. The machine is often decades old, the OEM may be gone and the drawing, if one exists, is a photocopy in a maintenance office. So the knife is ordered as a description, and the difference between a usable enquiry and a week of clarification emails is whether that description carries six things.

## Three dimensions, in the trade's order

The convention is length, then width, then thickness. A guillotine knife written as 820mm, 100 x 12mm is 820 long, 100 wide, 12 thick, and the leading standalone dimension before the knife type, as in an 820mm guillotine blade or a 100mm slitting knife, is always the length or the diameter. The trap for a reader, human or software, is that the length often arrives separated from the section: the 820 in the subject line, the 100 x 12 three sentences later, and a bore or a hole pattern in between waiting to be mistaken for one of them.

Figure: The six-part specification on one guillotine knife: length, section, steel, hardness, edge and bevel. The hole pattern rides along as a drawing or a sketch.

## The steel and the hardness

The grade names are a small, stable vocabulary: D2 for most general blanking and shearing work, M2 high speed steel where the edge must hold at temperature, O1 for easier grinding, 52100 and 440C in particular niches, carbide tipped and powder metallurgy grades at the hard end. The grade alone is half a statement; the working spec is grade plus hardness, written as a range, 58 to 60 HRC being the common shape. Two knives in the same D2 at different hardness behave as different products: harder holds an edge longer and chips more readily, softer forgives abuse and dulls sooner. A supplier quoting without the hardness is guessing on the customer's behalf.

## The edge is its own specification

The edge carries three decisions: the geometry, single bevel or double bevel, the finish, straight ground or hollow ground, and any tooth form, serrated or scalloped, for fibrous materials. The bevel angle in degrees completes it. These are not cosmetic: a single bevel knife cuts against a fixed anvil, a double bevel meets a second knife, and swapping them does not work. It is also the part of the spec most often missing from an enquiry, because the person reordering can see the length and measure the thickness, but the original bevel angle ground onto the knife is invisible without a gauge.

| What a quote needs | Where it usually is |
| --- | --- |
| Length, width, thickness | Split between the subject line and the body |
| Steel grade | Stated, or as 'same as last time' |
| Hardness range | Missing more often than present |
| Edge geometry and bevel angle | Missing unless a drawing comes with it |
| Hole pattern and fixings | A photo of the old knife with a tape measure |
| Quantity and whether regrinding is wanted | The last line, if at all |

Table: A complete machine knife enquiry against what typically arrives.

## Replace is only half the trade

A knife is a consumable with a service loop. Most run a regrind cycle, several sharpenings before the section falls below its working minimum, and the words resharpen and regrind in an enquiry signal a servicing job with its own price, turnaround and collection logistics rather than a supply line. A well run knife account is really a rotation: one set in the machine, one set at the grinder, one on the shelf, and the supplier who tracks the rotation owns the account.

> What Kabaido does. The Sales Engineer reads knife enquiries against exactly this specification: the dimension convention including the leading length rule, the steel grade and hardness vocabulary, the edge types and the servicing signals, each extracted value citing the words it came from. A missing hardness or bevel angle comes back as a structured clarification, not a guess.

Sources:
- Machine knife and industrial blade quoting on this site (/cutting-tools)
- Profile machine knives on this site (/cutting-tools/profile-machine-knives)
- The Kabaido cutting knowledge pack: the extraction vocabulary for saw blades and machine knives

## What a plasma cut chart actually encodes

URL: https://kabaido.ai/blogs/what-a-plasma-cut-chart-actually-encodes
Published: 2026-08-16. Category: Engineering notes.

A clean plasma part and an evening of grinding dross differ by three numbers per material and thickness. Where they come from and why they drift.

Two plasma tables can run the same machine, the same torch and the same sheet and produce different parts, because the part quality does not live in the hardware. It lives in a table of numbers: for each material at each thickness, how fast to move, how long to wait before moving and how wide the cut actually is. That table is the cut chart, and most of the craft knowledge in a profiling shop is really a set of amendments to it.

## Three numbers per row

A working chart holds at least three values per material and thickness. Feed rate, in millimetres per minute, is how fast the torch travels while cutting: too fast and the arc lags and leaves an unfinished kerf with heavy bevel, too slow and the arc wanders, the kerf widens and low speed dross builds on the bottom edge. Pierce time, in seconds, is how long the torch dwells after firing before it starts to move, while the arc blows through the sheet. Kerf, in millimetres, is the width of metal the arc removes, and it is the one that decides whether the part measures right.

Figure: One row per material and thickness: feed, pierce and kerf. A shop's own confirmed figures shadow the modelled starting values row by row.

## Kerf is half a number

The arc removes a slot of metal, not a line, so a torch driven along the drawn outline produces a part undersize by half the kerf on every edge. The controller therefore offsets the toolpath outward by half the kerf for outside profiles and inward for holes, which is why kerf appears in the chart as a full width but acts in the geometry as a half. It also explains two familiar shop truths: a hole always suffers more than an outside edge, because the compensation curvature is against it, and a kerf value that is 0.4mm out puts every edge 0.2mm out, so a width measured across two opposite edges is 0.4mm out.

## Pierce is where the failures cluster

Piercing is the violent part of the cycle. The arc has to blow molten metal back out of the hole it is making, so the machine pierces above the cut height, dwells for the pierce time, then drops and goes. Too short a dwell and the torch sets off before the sheet is through, ploughing a furrow instead of a cut. Too long wastes consumables and heat. Thick plate moves the problem sideways: the pierce happens away from the contour on a lead-in, so the crater the pierce leaves sits in scrap rather than in the part's edge.

## Whose numbers are they?

Manufacturers publish starting charts for their torch at each amperage, and they are exactly that, starting points. Every table settles into its own figures as consumables wear, as the shop learns what its air supply and its steel actually do, and as operators trade a little speed for a cleaner edge on the work they see most. The practical failure is that these amendments live in one operator's head or a notebook by the console, so the chart the software uses and the chart the shop believes drift apart, and every part cut in the gap between them carries the error.

> What Kabaido does. Arcline, the plasma machine module in Machinist, keeps one chart row per material and thickness. Rows start as modelled values and are marked as modelled until the shop saves its own figures, at which point the shop's row shadows the modelled one for that material and thickness. The nest, the cut plan and the G-code all read the same row, so the numbers the operator confirmed are the numbers the machine runs.

> A cut chart is a shop's memory of every bad edge it has ever produced. Software that ignores it throws that memory away.

Sources:
- Arcline, CNC plasma table and nesting software, on this site (/machinist/arcline)
- The Arcline cut model: per-material process parameters with modelled and confirmed states

## What a balustrade quote has to calculate

URL: https://kabaido.ai/blogs/what-a-balustrade-quote-has-to-calculate
Published: 2026-08-16. Category: Engineering notes.

A metre of balustrade looks like a price per metre. It is a structure with a load case, and the load case moves the price. The working, in order.

Ask a fabricator what balustrade costs and the honest answer is a question back: where is it going? A metre of the same glass and steel is a different product on a domestic landing, a balcony edge and the front of a bar, because each carries a different design load, and the load decides the post section, the post spacing, the glass makeup and the fixings before anyone gets to cut a length. A quote that starts from a price per metre has skipped the part of the job that was engineering.

## The load case comes first

UK guarding design starts from where people are and what they might do there. Approved Document K sets the guarding heights and points at BS EN 1991-1-1 with its UK National Annex and BS 6180 for the loads: a horizontal line load at the rail, a distributed load on the infill and a point load on the infill, all three of which the design has to satisfy. The line load is the one that moves most.

| Where the balustrade goes | Minimum height | Line load at the rail |
| --- | --- | --- |
| Single family dwelling, internal landing | 900mm | 0.36 kN/m |
| Single family dwelling, balcony or roof edge | 1100mm | 0.74 kN/m |
| Other residential and communal areas | 1100mm | 0.74 kN/m |
| Office and educational | 1100mm | 0.74 kN/m |
| Retail | 1100mm | 1.5 kN/m |
| Assembly, bars and crowd areas | 1100mm | 3.0 kN/m |

Table: Example guarding heights and line loads by use, as tabulated in the UK guidance. The designer confirms every value for the actual building.

Figure: The line load acts horizontally at the top of the guarding. The moment at each post base is the load times the bay width times the height, which is why the same post section spans different bays in different buildings.

## Post spacing is an output, not a preference

Each post resists the line load collected from the bay either side of it, acting at the guarding height. The moment at the post base is therefore load times bay times height, and a bay that works at 0.74 kN/m and 1100mm does not work at retail or assembly loading. A section tabled at 1500mm centres under the office band has its bay roughly halved at 1.5 kN/m and cut to about a quarter at 3.0 kN/m, and the scaling only ever narrows: a lighter duty never licenses a wider bay than the section's own table, because that limit is also a fabrication and infill limit, not only a strength one. More posts means more base plates, more fixings, more welding and more time, which is how the load case reaches the price.

## Glass is a makeup, not a thickness

Free standing glass protecting a drop is specified as a laminated makeup: two toughened leaves with an interlayer, written 8+8 with a 1.52 PVB for a 17.52mm build, 10+10 for 21.52mm, 12+12 for 25.52mm. The load case and the fixing method drive the choice, and the quote has to carry it as a makeup because the glass schedule, the weight the fixings see and the price per panel all follow from the build, not from a rounded thickness. A balustrade with a structural handrail and one without are different calculations for the same glass.

## Then the boring lengths

Only after the engineering settles does the familiar estimating begin, and even that is bookkeeping with consequences: posts at the derated centres against stock lengths, rail runs with joints placed away from bays that carry gates, panel widths that respect the post setting out, base plates and fixings per post, and a cutting list that someone on the saw will actually follow. Get the spacing wrong at the start and every line after it is wrong too, which is why the order of operations is the whole game: loads, then spacing, then glass, then lengths, then money.

> What Kabaido does. The Design Engineer balustrade configurator applies exactly this order: use class first, then the derated post spacing, then the glass makeup, then the cutting list and the priced quote, with every rule carrying the reference it came from. It applies dimensional rules and it says so plainly: it does not sign off a structure, and every engineering value is one the seller confirms before going live.

Sources:
- Approved Document K, protection from falling, collision and impact (https://www.gov.uk/government/publications/protection-from-falling-collision-and-impact-approved-document-k)
- BS 6180, barriers in and about buildings, and the UK National Annex to BS EN 1991-1-1
- Balustrade design software on this site (/design-engineer/balustrades-handrails)

## Choosing a bandsaw blade in three questions

URL: https://kabaido.ai/blogs/choosing-a-bandsaw-blade-in-three-questions
Published: 2026-08-16. Category: Method notes.

A bandsaw catalogue runs to hundreds of variants. The choice comes down to three questions and one rule about teeth. Here is the published maths.

A bandsaw blade catalogue runs to hundreds of variants: carbon, bimetal and carbide bodies, a dozen widths, twenty odd pitches, three tooth sets. Faced with that wall, most buyers reorder whatever is on the machine, which is how a blade specified years ago for one job ends up cutting everything badly. The choice is actually three questions, and only one of them needs any maths.

## What are you cutting? The pitch rule

The rule that decides tooth pitch is old, published and worth knowing by heart: count the teeth in the cut. Divide the engaged width of the workpiece in millimetres by 25.4 and multiply by the TPI, and the answer should land between 6 and 24 for metal, 3 to 6 for wood. Fewer than the minimum and the teeth straddle the work, snag and break. More than the maximum and the gullets pack with chips before they clear the cut, the blade rubs instead of cutting and the feed rate collapses.

Figure: The same 60mm bar against two pitches. Teeth in cut is engaged width over 25.4 times TPI; metal cutting aims for 6 to 24 teeth in the work.

| Solid section | Pitch (TPI) |
| --- | --- |
| Up to 5mm | 18 |
| 8 to 20mm | 8/12 |
| 16 to 30mm | 6/10 |
| 35 to 70mm | 4/6 |
| 60 to 120mm | 3/4 |
| 120 to 400mm | 1.5/2 |

Table: Published pitch guidance for solid sections. Bands overlap by design; where two fit, the coarser pitch cuts faster and the finer finishes better.

A pitch written as 4/6 is variable: the tooth spacing cycles between 4 and 6 TPI along the band, which breaks up the resonance that makes a constant pitch sing and lets one blade cover a range of sizes. The arithmetic still applies, run at the coarse value for the minimum teeth check and the fine value for the gullet check. Tube and structural sections have their own table because the engaged width is the wall, not the outside dimension, and it changes as the cut moves round the section.

## What machine is it running on? Length and width

The machine fixes two of the blade's dimensions outright. Loop length is pi times the wheel diameter plus twice the centre distance, with unequal wheels taken at their mean diameter, though the machine plate or the old blade settles it faster than the tape measure. Width is the widest band the guides and wheels accept, because a wider band is a stiffer band and a stiffer band cuts straighter. Run the widest blade the machine takes for every straight cut and only give up width when the work curves.

## How tight is the tightest curve? The width chart

| Blade width | Minimum radius |
| --- | --- |
| 6mm | 16mm |
| 10mm | 38mm |
| 13mm | 64mm |
| 19mm | 140mm |
| 25mm | 180mm |

Table: Published minimum contour radius by blade width. Between published points, interpolate and round up; tighter than the chart, no published width can turn it.

Contour work inverts the width rule: the blade must be narrow enough that its back clears the kerf as the cut turns. A 13mm blade will not turn a 40mm radius however carefully it is fed, it will bind, heat and wander. The honest reading of the chart runs conservative in both directions: pick the widest width whose published radius is inside the tightest curve on the drawing, and if the drawing asks for tighter than the narrowest published blade turns, the answer is a different process, not a hopeful attempt.

> Silver curled chips are right, powdery chips mean feed too low, blue chips mean speed or feed too high. (The chip check, as taught at the machine)

Band speed is the last variable and the one most often left wherever the last operator put it. The starting ranges are published per material family: free machining steels around 90 to 105 m/min, alloy steels 50 to 70, austenitic stainless 30 to 45 with constant feed and flood coolant because 304 work hardens the moment a tooth dwells, titanium down at 15 to 25. The chip check above is the feedback loop; the chart is only the starting point.

> How the Kabaido wizard applies this. The bandsaw wizard on this site runs exactly these published rules as deterministic code: the teeth in cut arithmetic, the pitch and speed charts and the width and radius chart, each answer carrying the name of the chart row it came from. Where a chart does not speak, outside its published widths for instance, the wizard says so rather than extrapolating. No model guesses a pitch.

Sources:
- Dakin-Flathers, bandsaw blade TPI selection chart (https://www.dakin-flathers.com/blog/bandsaw-blade-teeth-per-inch-tpi-chart)
- The Kabaido bandsaw wizard, on this site (/wizard)
- Kabaido wizard engine rules A1 to A13, published charts held as data

## The soft jaw order hiding in a chuck model

URL: https://kabaido.ai/blogs/soft-jaw-order-hiding-in-a-chuck-model
Published: 2026-07-10. Category: Engineering notes.

A soft jaw enquiry looks like two words and a chuck size. The serration, the jaw envelope and the material are all implied. How a seller reads one.

A soft jaw enquiry is one of the shortest a workholding seller gets. Two or three lines: a set of soft jaws for a 10 inch chuck, aluminium, as soon as you can. It reads like a stock pull. It is closer to a small engineering drawing with most of the dimensions left off, and the person quoting it fills the gaps from experience every single time.

That gap filling is the job, and it is the reason a low value order can sit for two days. The seller is not slow. The enquiry simply did not carry the things a jaw is actually defined by, so someone has to stop and go and get them before a price can exist.

## What the enquiry writes down, and what it leaves out

Usually you get a chuck size, sometimes a brand, a material family and a quantity. What you rarely get is the mounting interface, the exact chuck model, the grip direction, the workpiece diameter the jaws will be bored to, or the grip depth. Every one of those is needed to cut a jaw that fits and grips, and every one of them is normally recovered by a phone call or an assumption. The assumption is the dangerous part, because a jaw machined to the wrong interface is scrap, not a revision.

Figure: A soft jaw order carries a fraction of what a jaw is defined by. The rest is decoded from the chuck.

## The interface is a standard, and there is more than one

A top jaw does not just bolt on. It locates to the master jaw or the scroll through a serrated or a tongue and groove interface, and that interface is standardised. The catch for anyone quoting is that it is standardised to several patterns at once, and the chuck decides which. The two most common are a fine serration and a coarser one, each with a metric and an imperial form.

| Interface | Metric form | Imperial form |
| --- | --- | --- |
| Fine serration | 1.5mm at 60 degrees | 1/16 inch at 90 degrees |
| Coarse serration | 3.0mm at 60 degrees | 3/32 inch at 90 degrees |
| Tongue and groove | Slot and tenon to the chuck | American standard tongue and groove |

Table: The common chuck jaw mounting interfaces. The blank has to match the one the chuck was cut for, or it will not seat.

Which one you need is fixed by the chuck, not by the buyer's preference. A jaw cut with a 1.5mm serration will not sit on a chuck serrated at 3.0mm, and no amount of clamping force fixes it. This is why the mounting has to be read before anything is machined, and why sellers who carry the tables can turn an enquiry round while sellers who guess end up remaking blanks.

> Read the chuck model, not the chuck size. The diameter tells you almost nothing. The model number fixes the bolt pattern, the master jaw form and the serration. A 10 inch chuck is not a specification. A Kitagawa B-210 is, because its geometry is in a table you can look up.

## The material nobody writes down

The other silent field is material. Soft jaws are cut in aluminium or in steel, and the choice is not cosmetic. A 6000 series aluminium such as 6061 or 6082 is light, kind to a finished surface and quick to bore, which suits short runs and delicate parts. Steel holds a heavier grip and lasts longer under repeated clamping. The published examples make the point: WDS list their serrated soft top jaws in 080M15 steel, while the American standard tongue and groove jaws from Abbott are offered in 6061 aluminium in the T6 condition or in 1018 steel. Same product name, different metal, different price and different lead time, and the enquiry almost never says which.

Add the fields that decide the machining itself, the grip direction, the workpiece diameter the pocket is bored to, the grip depth and the quantity with its breaks, and a two line enquiry has quietly become a dozen decisions. An experienced estimator makes them in a couple of minutes. The cost is not the thinking. It is that the thinking cannot start until the missing half of the order has been chased down.

## Why this is a configuration problem, not a document problem

Step back and the shape of the work is clear. Almost nothing about a soft jaw is a judgement call. The mounting, the envelope and the blank size are a lookup against a chuck table the seller already owns. The material and its cost are a lookup against a stock list. The price is a formula. What the estimator supplies is not creativity, it is the table in their head and the discipline to apply it. That is precisely the kind of task software can hold, because every answer traces back to a source the seller already trusts.

That is the idea behind the soft jaws configurator. The buyer picks the chuck from the seller's own compatibility table, sets the workpiece diameter and the grip, and the serration, the jaw envelope and the blank size resolve from the table rather than from a reply two days later. Prices come from the seller's own formula, shown live. Where the loaded table does not cover a chuck, it says so and asks, rather than guessing at a mounting it cannot see. The seller stays the author of every rule. The software just does the decoding.

> A 10 inch chuck is not a specification. It is the first of twenty questions.

A set of soft jaws will always be a small order. The way to make it worth quoting is not to quote it faster by hand, it is to move the decoding, the chuck table and the price to where the buyer can do the easy part unaided, and to keep your engineers for the jobs that genuinely need them. The enquiry was never really short. It just left the hard half unwritten, and expected you to know it.

Sources:
- Serrated soft top jaws, 60 degree serrations and 080M15 steel, WDS Components (https://www.wdscomponents.com/en-gb/production-and-broaching/chuck-jaws)
- American standard tongue and groove soft jaws in 6061 aluminium or 1018 steel, Abbott Workholding (https://products.abbottworkholding.com/viewitems/chuck-jaws---accessories/groove-soft-jaws)
- Inch and metric serration soft top jaw standards, SMW Autoblok jaws catalogue (https://www.smwautoblok.com/us/en/catalogs/jaws/soft-top-jaws-inch-serration/)
- The soft jaws design module, on this site (/design-engineer/soft-jaws)

## What an RFQ actually contains

URL: https://kabaido.ai/blogs/what-an-rfq-actually-contains
Published: 2026-06-12. Category: Inside the work.

An RFQ looks like a document. It is closer to a scattered set of claims, each hiding somewhere else. How engineers read one, and how software should.

An RFQ looks like a document. Treat it as one and it will mislead you. What lands in an inbox is closer to a scattered set of claims: a quantity in the email body, a material in a standard reference, a tolerance in a drawing note, a delivery constraint in a forwarded thread two replies down. The skill of reading one is knowing where each claim hides and which ones are missing.

## The four questions

An experienced application engineer reads every request against the same four questions. What is being asked for. In what quantity. To what specification. For what application. Everything else in the document is either evidence for one of those answers or noise, and the fourth question is the one juniors miss: the application, often a single sentence of prose, regularly changes which product is right even when the specification is complete.

Figure: Where the answers hide in a typical RFQ. The highlighted strip is a source span: the exact text an extracted value points back to.

| What you need | Where it hides | What goes wrong |
| --- | --- | --- |
| Quantity | The email body, not the attachment | The quote prices the attachment's header quantity and the margin assumptions break |
| Material | A standard reference such as an EN or ASTM grade | A near-equivalent grade is substituted silently and surfaces at goods-in |
| Tolerance | A drawing note or the title block | The expensive one is missed and the part is quoted as standard |
| Application | One line of prose anywhere in the thread | The wrong product is configured perfectly |
| Commercial terms | A forwarded message or the customer's portal | Delivery and certification costs never reach the price |

Table: What a quote needs, where it tends to hide and what goes wrong when reading fails.

## Summarising is not reading

Most AI applied to documents produces summaries, and a summary is precisely the wrong tool here. Summarising compresses; quoting needs extraction. The job is to pull every attribute out as structured data, quantity as a number with a unit, material as a grade against a standard, each tolerance as a bound, and to keep the link back to the exact words it came from. We call that link a source span, and it is what turns a machine's reading into something an engineer can check in seconds rather than re-read in minutes.

> Cite or abstain. If a value is not in the request, the honest output is null plus a clarifying question, not a guess. An AI that invents a tolerance is worse than no AI at all, because the error arrives wearing the formatting of a fact.

> A missing specification is information. It tells you which question to ask before you price.

## Reading the way the engineer reads

This is the standard we hold our own extraction to. Kabaido reads a request against the same four questions, returns structured attributes with a source span on every value and abstains where the document is silent, surfacing the gap as a clarification to send back. The engineer stays the judge. The software just does the finding, so judgement is spent on the answer rather than the search.

Sources:
- How the Kabaido AI reads requests, on this site (/aei)
- Kabaido market research: the application engineer function map

## You cannot hire your way out of a quoting backlog

URL: https://kabaido.ai/blogs/you-cannot-hire-your-way-out-of-a-quoting-backlog
Published: 2026-06-10. Category: Industry research.

The UK posts about 900 new application engineer adverts a month against a 27,200 base. What continuous re-hiring of a hard-to-define role really signals.

Every month, UK firms post about 900 new job adverts for application engineers. The employed base is around 27,200. That is an advert flow running at roughly 3.3% of employment, month after month, for a role that takes years to grow and months to recruit. The market is not hiring this role in bursts. It is re-hiring it continuously.

- ~900: new application engineer adverts a month (Official series, AE-adjusted, grade B)
- 3.3%: monthly advert flow as a share of employment
- 186: live in-scope adverts in our snapshot (Grade C, the only independent measure)

## Flow and stock are different numbers

Those two demand figures look contradictory until you separate what they measure. The 900 is a flow: new adverts opened per month, read from official labour demand statistics. The 186 is a stock: adverts actually live on a given day. We report both and never average them, because the gap between them mostly measures how fast adverts turn over, not unmet demand. A market can post 900 adverts a month and only ever show 186 open if positions fill or expire quickly.

Figure: Flow in, stock held, filled or expired out. Averaging the two layers would produce a number that measures nothing.

## The adverts themselves are confused

Here is the strange part. When we pulled adverts for this role domain by domain, enormous fractions turned out not to be the role at all once reviewed. The title is used so loosely that in the sales-heavy domains most adverts wearing it were something else.

| Domain | Adverts out of scope |
| --- | --- |
| Bearings, motion and power transmission | 84% |
| Welding and joining | 65% |
| Sensors and industrial IoT | 64% |

Table: Out-of-scope rates among pulled adverts in the most confused domains, hygiene review of the 4 June 2026 snapshot.

That is not just a data-cleaning headache. It is a market signal in its own right. The role is hard to fill cleanly because it is hard to define cleanly. Firms reach for a title the labour market does not agree on, candidates cannot find the adverts meant for them, and the recruitment cycle stretches while the quoting queue grows.

## What continuous re-hiring signals

Persistent open demand for a scarce, expensive expert the taxonomy cannot pin down points to a structural capacity gap rather than a hiring blip. Each engineer costs around £50,115 gross, takes months to replace and arrives needing the firm's own catalogue, rules and pricing in their head before they quote at full speed. Meanwhile the requests keep arriving.

> Firms re-hire this scarce, expensive role continuously. That is a capacity gap wearing a recruitment costume.

The alternative lever is throughput: letting the engineers already in the building specify and quote more requests in the same hours, with software carrying the repeatable reading, configuring and calculating. Hiring still matters. But a backlog caused by a structural gap between request volume and specification capacity does not clear by adding one more person to a 3.3%-a-month treadmill.

> Read these figures as indicative. Live advert feeds over-represent churn-heavy, openly advertised roles, and the official series is a statistic in development with wide intervals. The April 2026 demand month sits just after a suppressed month. Directionally strong, decimally humble.

Sources:
- ONS and Textkernel online job advert estimates (statistic in development) (https://www.ons.gov.uk/employmentandlabourmarket)
- Adzuna live job adverts, UK snapshot of 4 June 2026 (https://www.adzuna.co.uk)
- Kabaido market research: UK demand analysis, snapshot 4 June 2026

## How to measure a market nobody counts

URL: https://kabaido.ai/blogs/how-to-measure-a-market-nobody-counts
Published: 2026-06-09. Category: Method notes.

No occupation code, no analyst report, no number to borrow. How we sized the UK application engineer market by triangulation, and kept it honest.

When we set out to size the application engineer market, we hit the problem that defines it: there is no number to borrow. No occupation code captures the role, so no official count exists, and the analyst reports that quote market sizes for adjacent software categories are built on those same codes. If we wanted a number we could stand behind, we had to build it, and show the working.

## Three legs, one estimate

The sizing triangulates three independent ways of looking at the same workforce. None of them is sufficient alone. Together they bound each other.

1. Top-down: start from official employment pools for the sixteen candidate occupation codes, then apportion each pool by the share of its live adverts that are genuinely this role. This leg sets the central estimate.
2. Bottom-up: count and classify live job adverts directly, domain by domain, after a manual hygiene review. This leg is noisier but independent of official weighting.
3. Register check: bound the result against the population of relevant companies on the register, asking whether the implied engineers-per-firm is plausible. This leg catches runaway estimates.

Figure: Three measurement legs converge on a central estimate of 27,200 with an envelope of 11,550 to 30,550. The envelope comes from the legs disagreeing, which is the point.

## Rules that keep the numbers honest

The mechanics matter less than the discipline around them. Six rules govern every figure we publish from this research.

- Grade every figure. Each number carries a confidence grade from A to D, and the grade is printed beside the number wherever it appears. A blend of two grades takes the lower one.
- Report the envelope, not just the centre. 27,200 means little without 11,550 to 30,550 beside it.
- Never average independent measurements. Our demand research reports a flow of about 900 adverts a month and a stock of 186 live adverts as two layers. The pair is the result.
- Date every snapshot. All figures in this body of research are stamped 4 June 2026 and will drift from that day onward.
- Pin the conversions. Currency uses the European Central Bank reference rate of 1 GBP = 1.34582 USD on the snapshot date, recorded with the data.
- Write the scope decisions down. 286 of 645 sampled adverts, 44%, were excluded after review, and the exclusion rules are documented so the cut is repeatable rather than convenient.

> Never present a modelled estimate as fact. (The first honesty caveat in our research notes)

## Why a software company publishes its workings

Partly because we would want the same from anyone selling to us. But mostly because the discipline is the same one our product runs on. Kabaido's AI is built to cite the source of every extracted value and to abstain rather than guess, and a company asking customers to trust that behaviour should hold its own market claims to the matching standard. A graded number you can check beats a confident number you cannot.

> The official sources have their own error bars. The underlying series, ONS four digit occupation estimates and the ONS and Textkernel advert series, are statistics in development with wide intervals and occasional source drops. Our grades inherit that uncertainty deliberately rather than hiding it.

The method is also portable. Because it starts from a national classification and a job-advert feed rather than anything UK-specific, the same three legs can size the role in any country that has both. Each new market becomes a dated, reproducible measurement rather than a rebuild, which is how we intend to grow the map.

Sources:
- ONS Annual Population Survey and ONS and Textkernel advert series (statistics in development) (https://www.ons.gov.uk/employmentandlabourmarket)
- Companies House register data (https://www.gov.uk/government/organisations/companies-house)
- European Central Bank reference rates (https://www.ecb.europa.eu)
- Kabaido market research: headcount, salary and demand analyses, snapshot 4 June 2026

## Where £1.36bn of quoting capacity sits

URL: https://kabaido.ai/blogs/where-1-36bn-of-quoting-capacity-sits
Published: 2026-06-08. Category: Industry research.

UK application engineer pay barely varies by domain, so headcount is the whole map. Three domains hold 41.7% of it. A tour of a top-heavy market.

The most surprising thing in our salary research is how boring the pay is. Across 19 industrial domains, every single one sits within 14% of the £48,892 advertised median for application engineers. A bearings specialist, a metrology engineer and a fluid power engineer all cost their employers roughly the same. Which means the interesting question is never what the role costs. It is how many of them each domain employs.

- £1.36bn: annual gross salary spend on UK application engineers (Grade C, envelope £482.6m to £1.85bn)
- 15,650: engineers in the five densest domains (Fluid power, machine tools, automation lead)
- within 14%: every domain's pay against the £48,892 median

## The top five domains

| Domain | Headcount | Share | Salary spend |
| --- | --- | --- | --- |
| Fluid power | 4,300 | 15.8% | £210.3m |
| Machine tools and CNC | 4,100 | 15.1% | £200.7m |
| Automation and robotics | 2,950 | 10.8% | £148.7m |
| Sensors and industrial IoT | 2,200 | 8.0% | £116.0m |
| Bearings, motion and power transmission | 2,100 | 7.8% | £106.0m |
| Top five together | 15,650 | 57.5% | £781.7m |

Table: Estimated UK application engineer headcount and salary spend, top five domains, snapshot 4 June 2026. Headcount grade B, spend grade C.

Figure: Headcount by domain, top five. Because pay is near-uniform, the headcount ranking and the spend ranking are the same list.

## Flat pay makes headcount the map

When pay varies a lot between segments, market maps get complicated: you weigh people against rates and argue about mix. Here the uniformity does the work for you. Salary spend and headcount rank the 19 domains in the same order, so one chart answers both questions. Where the engineers are is where the money is, and the engineers cluster hard. The top three domains hold 41.7% of headcount and 41.1% of spend. The top five hold 57.5% and 57.3%.

## A top-heavy market with thin tails

The tail is genuinely thin. Materials and metallurgy returned no in-scope live advert at all in our snapshot, and seven further domains rest on fewer than ten posting observations each, which is why their figures carry a C grade. This is not a market spread evenly across industry. It is a handful of dense domains, then a long quiet shelf.

For anyone building for this workforce, the concentration is the strategy. A product proven in machine tools, fluid power and automation reaches the majority of the spend while touching a fraction of the surface area. The same logic applies inside a distributor or manufacturer deciding where to standardise its quoting first: start where the engineers are.

> The lever on this £1.36bn is throughput per engineer, not price.

Because pay is flat and the work is repeatable, the spend is best read as the cost of human throughput on specification and quoting. Anything that lets one engineer specify and quote more, faster, moves that number directly. Hiring moves it too, in the wrong direction, and as we cover elsewhere on this blog, the market is already trying to hire its way out and struggling.

> Grade C, and gross rather than loaded. The value pool blends a grade C advertised salary fit with a grade B official anchor, and a blend takes the lower grade. The figures are gross salary, not fully loaded employer cost, so the true cost base sits above £1.36bn once on-costs are added. Envelope £482.6m to £1.85bn.

Sources:
- Kabaido market research: UK salary spend analysis, snapshot 4 June 2026
- Kabaido market research: UK headcount analysis, snapshot 4 June 2026
- ONS Annual Survey of Hours and Earnings, official pay anchor (https://www.ons.gov.uk/employmentandlabourmarket)
- European Central Bank reference rate, 1 GBP = 1.34582 USD on 4 June 2026 (https://www.ecb.europa.eu)

## Five tasks gate every industrial order

URL: https://kabaido.ai/blogs/five-tasks-gate-every-industrial-order
Published: 2026-06-05. Category: Inside the work.

An application engineer's week holds fifteen different jobs. Follow the orders instead of the diary and it collapses to five, all of them specification.

Watch an application engineer for a week and you will count fifteen different jobs. Watch where the orders come from instead and the week collapses to five tasks.

1. Capture the requirement: read the RFQ, the drawing, the GD&T callouts or the worn sample on the bench, and translate it into a defined requirement.
2. Design the solution: select and configure the product, process or system that meets it.
3. Specify the specials: engineer the custom and engineered-to-order items that fall outside the catalogue.
4. Run the calculations: feeds and speeds, cycle time, bearing life, clamping force, heat release or grid-code limits, whatever the domain demands.
5. Write the techno-commercial response: the proposal, the quotation, the RFP answer that carries all of the above to the customer.

Figure: The five specification functions form a spine from request to quote. The other ten functions of the role hang off it or recur from it.

## The spine is rules and calculation

In our function research these five came out as the pre-sale specification spine, each evidenced across at least three industrial domains and two industry families. That breadth matters: it means the spine is not a quirk of one sector. A fluid power engineer sizing a cylinder and a cutting tool engineer choosing an insert grade are doing structurally identical work with different tables. The same standards, the same designation systems and the same calculation patterns recur, request after request.

- 5 of 15: core functions form the specification spine
- 40 to 50%: of an application engineer's time spent on it
- Every order: gated by a specification someone must produce

## The other ten lean on it

The remaining functions of the role are real work, but they sit downstream of the specification or recur off it. A trial validates the configured solution. Commissioning installs what was specified. Troubleshooting revisits the specification under field conditions. Documentation and training describe it. Even account ownership is, at its core, the standing promise that the next specification will be right too.

> The most repeatable, most rules-and-calculation-heavy part of the role is also the part that bottlenecks every quote.

## Why the shape of the work matters

When a quoting queue forms in an industrial firm, it forms on the spine. Requests wait for the one person who can read the drawing, pick the configuration and stand behind the numbers. The instinct is to hire another engineer, and the market data says firms try continuously. But the shape of the work points at a different lever. Work that is repeatable, rules-based and calculation-heavy is work that software can carry most of, with the engineer judging the result instead of typing it.

A firm that wants more orders out of the same team does not need its engineers to do fifteen things faster. It needs the five tasks that gate every order to stop being a queue.

> Where the fifteen functions come from. The function library was built from job adverts and role descriptions across 19 industrial domains, from cutting tools to fluid power to automation. A function enters the core set only when it is evidenced in at least three domains and two industry families, so the spine reflects the role as the market actually advertises it.

Sources:
- Kabaido market research: the application engineer function map, 15 core functions
- Kabaido market research: UK problem intelligence, snapshot 4 June 2026

## The job title the labour market cannot see

URL: https://kabaido.ai/blogs/the-job-title-the-labour-market-cannot-see
Published: 2026-06-04. Category: Industry research.

Around 27,200 people in the UK do a job that official statistics cannot find. Here is what happens when a role spreads across sixteen occupation codes.

There are around 27,200 people in the United Kingdom doing a job that official statistics cannot find. They read customer drawings, size and configure products, run the calculations and write the technical quotes that industrial firms live on. Ask the firms and the role is obvious. Ask the labour market data and it dissolves.

- 27,200: employed application engineers in the UK (Central estimate, grade B)
- 16: candidate occupation codes the title spreads across (SOC 2020, grade B)
- 44%: of sampled job adverts out of scope on review (286 of 645 adverts)

## One role, three classifications

The trouble starts with the title. Application engineer maps to no single code in SOC 2020, the standard occupational classification the UK statistics system runs on. Depending on the wording of the advert alone, the same job lands in an engineering professional group (the 212x codes), an engineering technician group (311x) or a sales group (3552 or 3556). Across our crosswalk it touches sixteen candidate codes.

Figure: One role, sixteen candidate SOC 2020 codes across three classification families. The dashed lines are the problem: no single code owns the job.

The confusion runs deeper than coding. In a hygiene review of 645 job adverts pulled for the role, 286 of them, 44%, fell out of scope once the software developer sense of the title and pure sales roles with no engineering content were stripped away. The role straddles engineering and sales and sits cleanly in neither, which is exactly why the taxonomy keeps dropping it.

## Why an invisible role stays underserved

Software vendors size markets from occupation codes. Analysts build reports from them. Budgets get argued from headcount lines that roll up to them. A role split across sixteen codes never shows up anywhere as itself, so nobody builds for it, and the people doing the work inherit tools designed for someone else: CRM built for salespeople, CAD built for designers, spreadsheets built for everything left over.

> A function this large that the standard taxonomy cannot see is a function that standard tooling has not been built for.

## The numbers, with their error bars

Because no clean code exists, no off-the-shelf market figure exists either. The numbers below are triangulated from official employment pools, the composition of live job adverts and the company register, and each carries a confidence grade. We publish the grade beside the number on purpose: a graded estimate you can interrogate is worth more than a confident figure you cannot.

| Lens | Central estimate | Envelope | Grade |
| --- | --- | --- | --- |
| People | 27,200 employed | 11,550 to 30,550 | B |
| Money | £1.36bn gross salary a year | £482.6m to £1.85bn | C |
| Hiring | about 900 new adverts a month | 186 live in scope | B official, C live |

Table: The UK application engineer market in three measurements, snapshot 4 June 2026.

> Every figure here is a modelled estimate, not an official count. Headcount, spend and demand are triangulations built from ONS employment data, live advert composition and Companies House records. The grades run A to D and we never present a modelled estimate as fact. A separate post on this blog walks through the method in full.

## What the miscount costs

If you employ application engineers you already know the practical version of this story. They are scarce, they are expensive at a blended £50,115 gross salary per head, and when one leaves the replacement takes months because nobody can even agree what to put in the advert. The miscount is not a statistical curiosity. It is the reason the quoting bottleneck in industrial firms has stayed a people problem for decades while every adjacent function got software.

We built Kabaido for the work this role actually does, starting with the part that gates every order. But the first step was simply proving the role exists at scale, and that took counting a workforce the official numbers cannot see.

Sources:
- ONS Annual Population Survey, four digit occupation estimates (statistic in development) (https://www.ons.gov.uk/employmentandlabourmarket)
- SOC 2020, the UK Standard Occupational Classification (https://www.ons.gov.uk/methodology/classificationsandstandards/standardoccupationalclassificationsoc)
- Adzuna live job adverts, UK snapshot of 4 June 2026 (https://www.adzuna.co.uk)
- Kabaido market research: UK application engineer headcount analysis, 4 June 2026

## Teaching software to read like a domain engineer

URL: https://kabaido.ai/blogs/teaching-software-to-read-like-a-tooling-engineer
Published: 2026-06-01 (updated 2026-07-18). Category: Engineering notes.

A general AI model knows what a milling cutter is. It does not know your milling cutter. What it takes to ground a model in a real industrial domain.

A general language model knows what a milling cutter is. It has read every catalogue ever indexed. Ask it to recommend an insert grade for an interrupted cut in stainless and it will answer fluently, confidently and sometimes correctly. Fluency is the problem. In an industrial setting, an answer that cannot show where it came from is not an answer an engineer can sign.

## Domain knowledge is structured, not remembered

Machining knowledge is not a pile of prose. It is built on designation systems and standards that carry meaning in their structure. ISO 513, to take one load-bearing example, sorts every workpiece material into six application groups, and that single letter changes the cutting material, the geometry and the parameters that follow.

| Group | Workpiece materials |
| --- | --- |
| P | Steels, from free-cutting to high-alloy |
| M | Stainless steels, austenitic and duplex |
| K | Cast irons, grey and nodular |
| N | Non-ferrous metals, aluminium and copper alloys |
| S | Heat-resistant superalloys and titanium |
| H | Hardened steels and other hard materials |

Table: The six ISO 513 workpiece application groups.

Get the group wrong and nothing downstream can be right. A recommendation that treats duplex stainless as an ordinary steel is not nearly correct. It is wrong, and wrong in a way that costs inserts, machine time and trust. Domain grounding starts by giving the model these structures as structures, not as sentences it may or may not recall.

## The anatomy of a knowledge pack

For each industrial domain Kabaido covers, we build what we call a knowledge pack. Fifteen exist today, from cutting tools to MRO and workshop supply, and they sit at different depths. Eight carry the full stack described below. The rest carry their scope, vocabulary and extraction conventions while their corpus is built, so a request in those domains is still read and structured correctly, and any claim that needs a source waits for one.

Figure: The four layers of a domain knowledge pack. Answers come off the top with a citation, or not at all.

1. A corpus of authoritative sources: the standards, manufacturer catalogues and engineering handbooks the domain actually runs on, each recorded with provenance.
2. An authority map: an explicit ranking of which source wins when two disagree, so a marketing page never outranks the standard it paraphrases.
3. Structured tables: designation systems, parameter ranges and limits extracted into typed data the engine can compute against, not just retrieve.
4. An evaluation set: real requests with checked answers, kept apart from everything above, that the pack must pass before it ships.

## Evals before answers

The evaluation layer deserves the emphasis. A pack reaches full depth only once it carries a set of genuine RFQ-shaped requests with worked golden answers, and that test is stricter than getting the value right. A response only passes if it behaves the way a careful engineer would.

- It extracts what the request actually contains, with the exact source span for every attribute.
- It returns null for what the request does not contain, instead of filling gaps from prior knowledge.
- It raises a sensible clarifying question for each material gap.
- Its numbers survive unit conversion, because a thou is not a micron.

> An extraction you cannot trace is an opinion.

> The standing rule across every domain. AI output in Kabaido never invents a specification, tolerance, price or part number. Every extracted attribute carries a source span, and a missing value is null plus a clarification, not a guess.

None of this makes a model clever. It makes a model checkable, which in industrial work is worth far more. The engineer who signs the quote stays the judge. The knowledge pack just ensures that what reaches their judgement is grounded, cited and honest about its gaps.

Sources:
- ISO 513, classification of hard cutting materials by workpiece application group (https://www.iso.org/standard/59932.html)
- Kabaido domain knowledge packs and evaluation sets
- How the Kabaido AI grounds and cites its answers, on this site (/aei)

## Why quoting software should count in pence

URL: https://kabaido.ai/blogs/why-quoting-software-counts-in-pence
Published: 2026-05-28. Category: Engineering notes.

Binary floating point cannot hold a tidy decimal exactly. Charming in a tutorial, less so on a 4,000-line quote. A short defence of integer money.

Type 0.1 + 0.2 into a JavaScript console and it answers 0.30000000000000004. Charming in a tutorial. Less charming on a 4,000-line quote, where the same arithmetic runs thousands of times before anyone reads the total.

## Why floats cannot hold money

Computers store ordinary decimal numbers in binary floating point, and most tidy decimals have no exact binary form. One tenth in binary is a repeating fraction, the way one third is in decimal, so the machine stores the nearest value it can represent and the error tags along through every subsequent operation. The classics are worth seeing once.

| You write | You get |
| --- | --- |
| 1.03 - 0.42 | 0.6100000000000001 |
| 0.1 * 3 | 0.30000000000000004 |
| 1.005 rounded to 2 places | 1.00, because the stored value sits fractionally below 1.005 |

Table: Standard double-precision floating point arithmetic, exactly as a JavaScript console reports it.

Figure: The same sum in binary floats and in integer pence. One of these is exact every time.

## Integers and minor units

The boring, correct answer has been industry practice in payments for decades: store money as a whole number of the currency's minor unit, alongside the currency code. £189 is 18900 pence. Integer addition and subtraction are exact, comparisons are exact, and a column of a million line totals sums to the same value every time on every machine. The currency travels with the amount because the minor unit is not always two digits: yen has none and Bahraini dinar has three, so an amount without its currency is not even interpretable.

## Round once, at the edge

Calculation still needs fractions. A unit price times a quantity times a discount percentage produces values finer than a penny, and that is fine, as long as the fractions live in decimal arithmetic during the calculation and rounding happens once, at the final display. Round in the middle and the order you round in becomes part of the price.

| Policy | Working | Total |
| --- | --- | --- |
| Round each line, then sum | £11.00 + £11.00 + £11.00 | £33.00 |
| Sum, then round once | £32.985 rounded half-up | £32.99 |

Table: Three lines at £10.995 each, in exact decimal arithmetic, rounded half-up at different points.

Neither policy is wrong in the abstract. What is wrong is not choosing, because the moment your quote and your customer's ERP round in different places, a penny of disagreement appears on its own line in somebody's reconciliation report and an email thread starts that costs more than the penny ever did. Pick one rule, write it down and apply it everywhere.

> What Kabaido does. Money is stored as integer minor units with its currency. Calculation chains run in decimal arithmetic, never binary floats, and rounding is half-up, applied once at final display. Quote, order and invoice totals therefore agree with each other to the penny by construction.

A quote is a promise about a number. The arithmetic behind it should be the most trustworthy thing in the building, which is why the first engineering decision in any quoting system worth the name is also the least glamorous one: count in pence.

Sources:
- IEEE 754, the floating point standard behind the examples (https://en.wikipedia.org/wiki/IEEE_754)
- ISO 4217 currency codes and minor units (https://www.iso.org/iso-4217-currency-codes.html)

# Documentation

# Docs: Getting started

## Create your account

URL: https://kabaido.ai/docs/getting-started/create-your-account

Sign up and set up a workspace around your trade, your products and your presets in a few short steps.

Why: A workspace set up around the work you do is useful from the first request.
What: Sign up, then answer a few short screens: your name, your organisation and trade, your products and your presets.
How: Start at [Start free](/signup); everything you choose can be changed later in Settings.

### Sign up

Choose **Continue with Google** or **Continue with Microsoft** where they are offered, or **Sign up with email** with your work email and a password. If a confirmation link is sent, open it and setup starts. No card is needed.

### The setup screens

1. **What should we call you?** Type your name.
2. **What is your organisation called?** Type the name, then answer **What does your business do?** by picking up to three trade cards, the closest first. Your first pick leads.
3. **What does your business need?** Pick your products. Your trade's products arrive ticked; change any of them now or later in Settings. At least one is needed.
4. **What do you sell or service?** Tick the presets for your range; your trade's arrive ticked, and a preset that needs a product you have not picked shows muted. Press **Finish setup**, or **Skip for now** with nothing ticked.

### What each trade pre ticks

| Trade card | Products pre ticked |
| --- | --- |
| Cutting tool manufacture | Sales Engineer, Design Engineer, Stock, Machinist and Wizard |
| Regrind and servicing | Service Centre and Sales Engineer |
| Tooling and industrial distribution | Sales Engineer, Stock and Wizard |
| Subcontract machining | Sales Engineer, Machinist and Stock |
| Fabrication and made to order work | Sales Engineer, Design Engineer, Machinist and Stock |
| Profile cutting and plasma | Sales Engineer, Machinist and Stock |
| Balustrades and architectural metalwork | Sales Engineer and Design Engineer |
| Something else | Sales Engineer |

Arriving from a product's page on the website also ticks that product. Pre ticking is a suggestion only: every tile stays selectable and no product needs another.

> Nothing is invented for you: no sample products, customers or prices. Presets install real setup you can edit, and their services arrive switched off, so nothing quotes a figure you have not set.

### Joining by invitation

An invitation opens **Join** followed by the organisation's name. Confirm your name and you arrive with the role, areas and stations the invitation carried; the organisation, products and presets steps are skipped. Sign in with the address the invitation was sent to.

## Set up your organisation

URL: https://kabaido.ai/docs/getting-started/set-up-your-organisation

Set the details, numbering and brand that every quote, order and document carries.

Why: Your VAT rate, numbering and logo are on every document a customer keeps, so they are worth setting once, early.
What: Settings then Organisation holds the company details, the brand, document numbering, terms, customer fields and stations.
How: Open `/app/settings/organisation` as an admin or owner and work through the tabs.

### The tabs

| Tab | What you set |
| --- | --- |
| **Company** | Name, currency, VAT number and rate, the inspection approval delta, the order price tolerance, brand colour, logo, company details, address and default terms |
| **Templates** | Document IDs (quote, order and serial prefixes, number width, year segment) and named terms templates; with Source on, its own prefixes and tolerances too |
| **Customer fields** | Extra fields on every customer record, carried through CSV import and export |
| **Stations** | The benches, machines, docks and vans that sign in with their own device key |
| **What the AI has learned** | Preferences the AI keeps once a correction has been confirmed three times; **Forget** removes one |

### Set these first

1. On **Company**, set the currency and the VAT rate, then **Save organisation**. The rate decides whether a total is right.
2. Press **Upload logo** (any image but SVG; large files are resized) and pick a **Brand colour**. Both appear on quote PDFs, emails and the pages your customers open.
3. On **Templates**, set the prefixes and **Save document IDs**. Existing numbers never change.

> Logos and colours apply on every plan. On the Free plan a document also carries the Kabaido wordmark and a Prepared with Kabaido line; Pro, Ultra and Max carry your branding alone.

### What lives elsewhere

Where your customers sign in, and how it looks to them, is set under Settings then Customer facing, brought by Commerce: see [customer facing settings](/docs/commerce/customer-facing-settings). People and their access are under [Users, roles and stations](/docs/getting-started/users-roles-and-permissions).

### Danger zone

Only an owner sees **Delete organisation**, which asks you to type the workspace slug. It removes all of its data and cannot be undone, so [export your data](/docs/security/data-export-and-deletion) first.

The foot of **Company** shows the **Platform version** your workspace runs.

## The first run and the tours

URL: https://kabaido.ai/docs/getting-started/the-product-tour

Know what the first run shows you, how each area explains itself and how to replay any of it.

Why: A new workspace should explain itself on the real screens, not in a slideshow.
What: Two short tours on first sign in, the AI interface then the menu, and a short guide in each area the first time you open it.
How: Follow the cards with the buttons or the arrow keys; replay them from **Restart tour** whenever you like.

### The first run

1. A welcome card, with a line for the trade you picked first.
2. The AI interface at `/app`: the box, the mode chips, what the AI works across in your workspace, the usage bar, the quick actions and the threads.
3. The menu: the rail, one stop per group you actually see, your stations if you hold any, search, and **Start with** the area your trade leads on.

The tour is built from your own menu, so it never points at an area your products or your access do not include. On a narrower screen, where the rail sits behind the menu button, it points at the button instead.

### A guide in every area

The first time you open an area, a short guide walks its screen once. **Skip this guide** closes it for good. Skip two in a row and Kabaido asks **Turn these guides off?**, with **Keep them** and **Turn them off**.

A guide never starts while a dialog is open or you are typing in a field.

### Moving through a tour

- **Next** and **Back**, or the arrow keys.
- Esc leaves the tour where it stands.
- **Skip the tour** ends it, and it does not reopen by itself.

### Replaying it

1. Press Ctrl and K (Cmd and K on a Mac) and choose **Restart tour**, or open `/app/settings/profile` and press **Restart tour** under **Product tour**.
2. From the palette the tour starts again at once; from the profile page it starts the next time you open `/app`. Either way the guides you skipped come back.

## Finding things fast

URL: https://kabaido.ai/docs/getting-started/finding-things-fast

Search everything from the menu and jump anywhere with the command palette.

Why: Finding a record should take one box, not a hunt through areas.
What: Search in the menu looks across your records; the command palette jumps to an area or starts an action.
How: Press **Search** at the top of the menu, or Ctrl and K (Cmd and K on a Mac) anywhere.

### Search in the menu

Press **Search** and the row becomes a box in place. Type at least two characters and results appear grouped by type: products, customers, service items, quotes, orders and requests. Where a type has more than it shows, **All** with the count opens that area filtered to your term. The arrow beside the box, **Back to the menu**, returns to the menu.

A link to `/app/search?q=` opens this same search with the term typed in, so old bookmarks still work.

### The command palette

Ctrl and K opens it on any screen. It offers actions such as **New request**, **New quote**, **New customer**, **Import products** and **Restart tour**, and jumps to any area or view you have. It is keyboard first throughout.

### Which to reach for

| You want to | Use |
| --- | --- |
| Get somewhere or start something | The command palette |
| See every record that mentions a term | Search in the menu |
| Find an earlier conversation with the AI | **Recents** in the menu, or **All chats** beside it to search every one |
| Browse the catalogue by attribute | The Catalogue's filter rail, built from your own fields |

### The account menu

The account button at the foot of the menu, showing your organisation's name, opens **Settings**, **Ask for help**, **Support**, **Documentation**, the theme switch and **Log out**. The palette offers **Documentation** too.

## Users, roles and stations

URL: https://kabaido.ai/docs/getting-started/users-roles-and-permissions

Invite people by the job they do and give each one the role, areas and stations that job needs.

Why: Each person should see the work they do and change only what their job owns.
What: A role decides what someone can change, their areas decide what they see, and their stations are where they can work.
How: Invite from `/app/settings/users` with a role template, then adjust anyone's access later.

### Invite someone

1. Open `/app/settings/users` (admins and owners only).
2. Under **Invite a teammate**, type their email and pick a **Role template**, or **Customise** the role, areas and stations yourself.
3. Press **Invite**. They receive an emailed link; until they accept, it sits under **Pending invitations** with **Resend** and **Revoke invite**.

### Role templates

One per job. Only the templates that fit your products are offered, and **Save as a template** keeps any member's setup as your own.

| Template | Role | Areas | Stations |
| --- | --- | --- | --- |
| Internal Sales | Sales | AI, Quotes, Orders and Customers | None |
| Applications Engineer | Engineer | AI, Quotes, Orders, Customers, Catalogue, Design, Wizard and Servicing | None |
| Estimator | Sales | Quotes and Catalogue | None |
| Buyer | Engineer | Suppliers, Orders and Stock | None |
| Stores | Engineer | Stock, Orders and Scan | Scan |
| Service Manager | Engineer | Servicing, Orders and Customers | None |
| Bench Operator | Operator | Servicing | Bench |
| Production Manager | Engineer | Machinist, Orders and Stock | None |
| Operator | Operator | Machinist and Scan | Machine and Scan |
| Transport Manager | Engineer | Route and Orders | None |
| Driver | Operator | Their stations only | Driver |
| Field Sales | Sales | Inspect, Customers and Route | None |
| Marketing | Sales | Inspect, Commerce and Wizard | None |
| Finance | Viewer | Orders, Customers, Suppliers and Billing | None |
| Administrator | Admin | Every area | None |

### The roles

| Role | What it allows |
| --- | --- |
| Viewer | Read only. Sees requests, quotes, orders, customers, the catalogue and servicing but cannot create or change anything. |
| Operator | Works at a station: scans items in and out, records what was done and moves a job along. Never sees a price, a cost or a margin, and reaches no settings but their own profile. |
| Sales | Everything a viewer sees, plus creating and editing requests, quotes, orders and customers. |
| Engineer | Everything sales can do, plus managing the catalogue, catalogue schemas, design modules, servicing and stock. |
| Admin | Everything an engineer can do, plus organisation settings, members and invitations, pricing rules, special prices, integrations, API keys and imports. |
| Owner | Everything an admin can do, plus billing and the subscription plan. |

Roles are enforced by the database on every route, not only hidden in the screens. Only an owner can make an owner, and the last owner cannot be removed.

### Areas per member

Press **Access** beside a member to set **Areas** (**Every area**, or only the ones you tick) and **Stations**, then **Save access**. An area left off disappears from their menu and from what the AI offers them; Settings always keeps their own profile.

### Stations in the menu

A member who holds stations sees **Stations** below the area groups in the menu. Opening one runs that station's screen under their own sign in, records both the station and the person on every scan and step, and **Back to workspace** returns them in one click.

Stations are created, and their device keys issued, under Settings then Organisation, **Stations**. A shared screen nobody is signed in to still uses its device key at `/station`.

## What a free workspace holds

URL: https://kabaido.ai/docs/getting-started/what-a-free-workspace-holds

Know what the free plan includes, where its caps are and what stops when one is reached.

Why: The free plan is there to see how the platform works on your own data before you subscribe.
What: Every product can be switched on; the plan sets caps on scale and a small AI allowance that does not refresh.
How: Choose products at sign up as anyone else would; an owner or admin sees the caps under Settings then Billing.

### Every product is available

Products are switched on by need, never by plan, so a Free workspace can have any of them. Onboarding is the same on every plan.

### The caps

| What | On Free |
| --- | --- |
| Users | 2 |
| Catalogue products | 100 |
| Services | 2 |
| Design modules | 2 |
| Saved designs | 5 |
| Design exports a month | 10 |
| Wizard runs a month | 10 |
| Stations | 1 |
| Storage | 250 MB |
| Inspect | A preview: the map and the lists, with no profile opened |
| Customer sign in, with Commerce | The path form, `kabaido.ai/c/<prefix>`; a prefix address comes with a paid plan |
| Documents | Your logo and colours, plus the Kabaido wordmark and a Prepared with Kabaido line |
| AI | An allowance for the life of the account, enough to put a few real enquiries through; it does not refresh |

### What stops at a cap

- The next one is refused with a message naming the plan limit: another invite, product, service, saved design, export or wizard run. Nothing already made is removed.
- When the AI allowance is used, AI answers stop. Quoting, the catalogue and everything you do by hand carry on as normal.
- The monthly caps start again each calendar month.
- Upgrading lifts a cap and refreshes usage straight away.

> Settings then Billing shows every cap except wizard runs under **Scale**, beside what you have used. Usage itself is never shown as a unit count, on any plan.

Compare the plans on [Pricing](/pricing).

## Getting help

URL: https://kabaido.ai/docs/getting-started/getting-help

Ask in the AI area, read the docs, or open a ticket for the team.

Why: An answer should be one question away, in the place you already ask everything else.
What: Help lives in the AI area, answered from these docs, with a person one step behind it.
How: Press **Ask for help** in the account menu or on the Support page, or just ask in Question mode.

### Asking a question

Ask in **Question** mode. A question about how the platform works is answered from this documentation, with the articles linked beneath. A technical question about your work is answered from the engineering knowledge behind your industry.

Asking Kabaido for help never draws on your workspace's monthly usage.

### When a person is needed

If the docs do not answer it, if your account needs a change or something looks broken, help prepares a ticket and shows you what it says. Nothing is sent until you press **Open the ticket**.

### The Support page

`/app/support` reaches the team without asking first: **Send a message** opens a ticket and **Book a call** picks a slot from real availability. Use it for your account or billing, data that looks wrong, a bug, or a quote for a Commerce website, a design module, a wizard or a machine build.

Your tickets sit there too, open ones first. Open one to read it, then **Mark resolved**, **Close** or **Reopen**.

> Tickets are read by the Kabaido team. Put nothing in a ticket you would not send us by email.

### What help is not

Help cannot read or change your data and cannot change your plan. Questions about your own records belong to the AI area's other capabilities, which read your workspace through your own role.

## Support and availability

URL: https://kabaido.ai/docs/getting-started/support-and-availability

Know how to reach us, what each plan's support includes and what we do and do not promise about uptime.

Why: You should know before you need us how to reach us and how quickly we answer.
What: Help in the AI area, tickets, email and calls, with support that grows with the plan.
How: Ask in the AI area first; open a ticket or book a call when a person is needed.

### How to reach us

- Help in the AI area, and tickets on the Support page. See [Getting help](/docs/getting-started/getting-help).
- Email hello@kabaido.com, which reaches the same team as a ticket.
- Book a call from [Contact](/contact), which shows real availability.

### Support by plan

| Plan | Support | Help wiring up integrations |
| --- | --- | --- |
| Free | Docs | Not included |
| Pro | Email support | Not included |
| Ultra | Priority email support | Included |
| Max | Priority support with a named contact | Included |

### Reply times

A person reads your message and replies, usually within one working day. That is a target we hold ourselves to, not a contractual response time; a contractual one belongs in an [Enterprise](/docs/billing/enterprise) agreement. Priority means we work those tickets before the rest of the queue.

### Availability

We work to keep the service available, fix faults promptly and give reasonable notice of planned maintenance. There is no uptime guarantee unless an Enterprise agreement states one, as the [Terms of Service](/legal/terms) set out.

> We do not publish an uptime percentage, because we do not yet measure one you could rely on.

### Reporting a security issue

Write to hello@kabaido.com and a person reads it. The process is on [Platform and payment security](/docs/security/platform-and-payment-security).

# Docs: The platform

## Products, areas and parts

URL: https://kabaido.ai/docs/platform/products-areas-and-parts

Tell a product from an area and a part, know what you install inside a product and where each one shows up.

Why: One vocabulary makes every screen, every doc and every conversation with us mean the same thing.
What: Products are what you switch on, areas are where you work and parts repeat across areas; and some products take a design module, wizard module, machine module or service model you install.
How: Switch products on in Settings then Products; the areas, views and parts follow on their own.

### Products

What a workspace switches on by need, never by plan, in [Settings then Products](/docs/areas/settings#products).

| Product | Element | What it does |
| --- | --- | --- |
| [Sales Engineer](/docs/sales-engineer) | Sales | Sales Engineer answers the technical customer request, from the enquiry arriving to the quote or order going back. |
| [Design Engineer](/docs/design-engineer) | Sales | Design Engineer turns a custom enquiry into a configured, priced and drawn product. |
| [Route](/docs/route) | Logistics | Route takes the confirmed order and gets it to the customer's door. |
| [Source](/docs/source) | Logistics | Source runs your buy side, from the request for quotation to the invoice matched against what arrived. |
| [Stock](/docs/stock) | Logistics | Stock keeps one true quantity for everything you hold, wherever it is. |
| [Service Centre](/docs/service-centre) | Production | Service Centre runs the work you do on the customer's own property, from the item arriving to the item going back. |
| [Machinist](/docs/machinist) | Production | Machinist runs the floor and tells you what the job cost. |
| [Wizard](/docs/wizard) | Marketing | Wizard picks the right product for the application, the way an application engineer would. |
| [Inspect](/docs/inspect) | Marketing | Inspect tells your sales team which manufacturers to approach and what to say when they get there. |
| [Commerce](/docs/commerce) | Marketing | Commerce puts your catalogue online as a B2B trade site and connects it to the platform. |

### Areas

The places you work. An area is there when any product that brings it is on, and its **views** are whatever your products add.

| Area | Where | Kind | Menu group |
| --- | --- | --- | --- |
| [AI](/docs/areas/ai) | `/app` | In the menu |  |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | In the menu | Sales |
| [Orders](/docs/areas/orders) | `/app/orders` | In the menu | Sales |
| [Customers](/docs/areas/customers) | `/app/customers` | In the menu | Sales |
| [Suppliers](/docs/areas/suppliers) | `/app/suppliers` | In the menu | Sales |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | In the menu | Products |
| [Stock](/docs/areas/stock) | `/app/stock` | In the menu | Products |
| [Servicing](/docs/areas/servicing) | `/app/servicing` | In the menu | Products |
| [Design](/docs/areas/design) | `/app/design` | Full screen workbench | Products |
| [Wizard](/docs/areas/wizard) | `/app/wizard` | Full screen workbench | Products |
| [Machinist](/docs/areas/machinist) | `/app/machinist` | Full screen workbench | Operations |
| [Route](/docs/areas/route) | `/app/route` | Full screen workbench | Operations |
| [Inspect](/docs/areas/inspect) | `/app/inspect` | Full screen workbench | Growth |
| [Commerce](/docs/areas/commerce) | `/app/commerce` | Full screen workbench | Growth |
| [Settings](/docs/areas/settings) | `/app/settings` | Settings |  |
| [Scan](/docs/areas/scan-station) | `/app/scan` | Station screen |  |

### Parts

Parts never have a menu entry. They appear inside areas as a panel, a button or a field, shaped to where you meet them.

| Part | What it is |
| --- | --- |
| [Pricing](/docs/parts/pricing) | Discounts, special prices, margins, quantity breaks and price brackets per customer, product, service or group, at scale |
| [Costing](/docs/parts/costing) | Cost against a product, against time, against machines, against stock and formulas, everywhere a margin needs to be real |
| [Customer context](/docs/parts/customer-context) | Custom fields, history, patterns and interactions behind every customer, feeding the AI without leaking or guessing |
| [Monitoring](/docs/parts/monitoring) | Watchers set against any area that act when something changes |
| [Traceability](/docs/parts/traceability) | One Kabaido code on any item, batch, package or job, scannable and followed through the platform and the workshop |
| [Integrations](/docs/parts/integrations) | Every connection to the systems around the workspace, tailored per product, plus custom ones |
| [Roles](/docs/parts/roles) | Who sees what and does what, per person and per station |
| [Presets](/docs/parts/presets) | Ready made setup for a trade, applied at onboarding or later |
| [Customer facing](/docs/parts/customer-facing) | The org's own customers on a branded surface of the same platform |
| [Activity](/docs/parts/activity) | Every action recorded, and the notifications the team and the org's customers receive |
| [Documents](/docs/parts/documents) | Quotes, orders, dockets, drawings, work orders, labels and attachments, templated and branded |

### What you install inside a product

Design modules in [Design Engineer](/docs/design-engineer), wizard modules in [Wizard](/docs/wizard), machine modules in [Machinist](/docs/machinist) and service models in [Service Centre](/docs/service-centre). Presets install them. Each design, wizard and machine module opens as its own workbench; service models sit in the **Services** view of Servicing.

## How your workspace adapts

URL: https://kabaido.ai/docs/platform/how-your-workspace-adapts

Predict what appears, what stays and what goes when a product is switched on or off.

Why: A workspace should carry exactly what the business does, and grow without a migration.
What: The menu, the views, the AI's capabilities, the tours and the setup checklist are all worked out from the products that are on.
How: An admin or owner switches products at `/app/settings/products`; everything else follows.

Screenshot of /app/settings/products: Settings then Products: a card per product with its first sentence and its switch.

### The union rule

- An area is present when any product that brings it is on.
- Its views are the union of what the products that are on add. Nothing is duplicated.
- A contribution, a product adding to an area it does not bring, appears only when both products are on.

Orders shows it well. Each view appears with a product that adds it:

| Orders view | Added by |
| --- | --- |
| Sales | Sales Engineer, Design Engineer, Service Centre, Wizard and Commerce |
| Purchase | Source |
| Production | Machinist |
| Deliveries | Route |

### Switching a product off

- Nothing is deleted.
- Its area stays readable with a banner, and writes there are refused.
- Its menu entry moves to the foot of its group, and disappears once the area has no rows.
- The AI stops offering it: a read only area offers no AI.
- At least one product always stays on.

Switch it on again and the area, its views and the AI's capabilities come back with every row intact.

### Works with, never needs

No product requires another. Where two add to each other, the product card says so:

| Product | Works with |
| --- | --- |
| [Design Engineer](/docs/design-engineer) | Stock and Commerce |
| [Route](/docs/route) | Stock and Commerce |
| [Source](/docs/source) | Stock |
| [Stock](/docs/stock) | Design Engineer, Route, Source, Service Centre and Machinist |
| [Service Centre](/docs/service-centre) | Stock and Commerce |
| [Machinist](/docs/machinist) | Stock |
| [Wizard](/docs/wizard) | Commerce |
| [Commerce](/docs/commerce) | Design Engineer, Route, Service Centre and Wizard |

### Access narrows it further

A member's role and areas narrow the same workspace for them: an area left off their list leaves their menu and their AI capability list. See [Users, roles and stations](/docs/getting-started/users-roles-and-permissions).

Interactive example: The Products switchboard beside the menu the registry computes for it.

## The AI interface

URL: https://kabaido.ai/docs/platform/the-ai-interface

Use the one AI input: pick the right mode, find past threads and know what it can do in your workspace.

Why: An application engineer does not open a different assistant for each part of the job.
What: `/app` is the one AI input in the platform, and what it can do follows your products, your role and your areas.
How: Type or attach what arrived, pick the mode and send.

Screenshot of /app: The AI area in a new workspace: the one input with its Request, Order and Question modes, and the suggested starts below.

### One input

No other area has an AI box. Where a screen benefits, a quiet link opens `/app` with the prompt written for you, never sent:

| Link | Where |
| --- | --- |
| **Build a meeting agenda** | Inspect |
| **Draft a price list** | Inspect |
| **Debrief this visit** | Inspect |
| **Build this from what we sell** | Inspect |
| **Ask about this design** | Design |
| **Read these columns** | Catalogue |
| **Ask for help** | Support and the account menu |
| **Ask about this customer** | Customers |

### The modes

| Mode | Use it for |
| --- | --- |
| **Request** | An enquiry to price, an RFQ or a drawing. Every line is set out, matched against what you sell or service, then drafted into a quote. |
| **Order** | A purchase order to raise, a PO. Lines are matched and checked against the quote they came from, then drafted into an order. |
| **Question** | A question, technical or about your own work, answered with its sources. |

**Question** is always there. **Request** and **Order** appear when Sales Engineer, Design Engineer, Service Centre, Wizard or Commerce is on, your role is sales or above and your areas include Quotes (for Request) or Orders (for Order). The mode decides what comes back, so the AI never guesses.

### Your chats

Every conversation is a chat you can reopen. The latest sit in the menu under **Recents**, on every screen, with the pinned ones above them. **All chats** beside the heading opens the whole list, and its search finds a chat by its title or by anything asked in it.

Each chat offers **Rename**, **Pin** and **Archive**, and an archived one **Restore** from All chats; nothing is deleted. On a narrower screen Recents are in the menu behind the menu button.

### What it can do here

**What this can do here**, beside the modes, lists what the AI can do for you in this workspace, narrowed by your role and your areas. A product you do not have is not listed; ask for it anyway and the AI says which product would answer.

| Product | What the AI can do |
| --- | --- |
| Every workspace | Ask a technical question and get help with Kabaido |
| [Sales Engineer](/docs/sales-engineer) | Answer a request for quotation, raise an order from a purchase order and ask about your catalogue |
| [Design Engineer](/docs/design-engineer) | Answer a request for quotation, raise an order from a purchase order and configure a custom product |
| [Route](/docs/route) | Track a delivery and see today's deliveries |
| [Source](/docs/source) | Ask suppliers for a price and check a purchase order |
| [Stock](/docs/stock) | Check stock and adjust or move stock |
| [Service Centre](/docs/service-centre) | Answer a request for quotation, raise an order from a purchase order, price service work, price a batch of items, look up an item's history and see what is due |
| [Machinist](/docs/machinist) | Check a job on the floor, check the schedule and capacity and make a job from a request |
| [Wizard](/docs/wizard) | Answer a request for quotation, raise an order from a purchase order and pick the right product with a wizard |
| [Inspect](/docs/inspect) | Prepare a visit agenda, draft a price list, debrief a visit and build your offering map |
| [Commerce](/docs/commerce) | Answer a request for quotation, raise an order from a purchase order, reply to a website enquiry, read your website's numbers and see who uses your customer sign in |
| Wherever the Catalogue is | Read a spreadsheet's columns |

The usage bar at the top right of the box moves as an answer finishes: one allowance for the whole workspace, shared by everyone in it. See [how usage works](/docs/billing/how-usage-works).

Interactive example: The capability list for three product setups, resolved by the real registry.

## Application Engineering Intelligence

URL: https://kabaido.ai/docs/platform/application-engineering-intelligence

Understand the knowledge behind every AI answer: seven categories over fifteen knowledge packs, selected per request.

Why: A request is only useful once it is read in your industry's own terms.
What: AEI is Kabaido's working model of the UK industrial supply chain: the knowledge of an application engineer, built in.
How: Nothing to configure: every workspace has all of it, and each request draws on the packs it needs.

### Seven categories, fifteen packs

Each knowledge pack carries the vocabulary, designation grammar and extraction conventions of one supply area.

| Category | Knowledge packs |
| --- | --- |
| Cutting tools and abrasives | Cutting tools and Abrasives and grinding |
| Machines, workholding and automation | Machine tools and CNC, Workholding and toolholding, Hydraulics and pneumatics and Power transmission |
| Fabrication and joining | Welding and joining, Sheet metal and fabrication and Fasteners and fixings |
| Measurement and quality | Metrology and inspection |
| Surface engineering and heat treatment | Coatings and heat treatment |
| Materials and stock | Materials and stock and Plastics and composites |
| Fluids, consumables and workshop | Fluids and lubricants and MRO and workshop |

### Selected per request

A quick scan of each request picks only the packs it needs before any model runs, so a bearing enquiry is read with power transmission knowledge and a regrind list with cutting tool knowledge.

Interactive example: Real request lines lighting only the packs the prescan selects.

### What AEI does with a request

1. Reads the text, tables and scanned pages you sent into one document.
2. Sets out each line with its units normalised and a citation behind every value.
3. Fills a missing detail only where your customer's own history or the stated application settles it, and shows it as an assumption you can change.
4. Matches each line by calculation against your catalogue, your designs and your services.
5. Answers with the matches, the questions it still needs answered and the draft.

### Your data is the authority

The packs know what a designation means. What you stock, charge or will substitute comes from your own catalogue, fields and pricing, which is why the same enquiry gives two businesses two different answers, each right for the business that received it.

> Cite or abstain: AEI never invents a specification, tolerance, price or part number. A value the request does not state stays empty and becomes a question.

AEI sits behind every product that reads a request. More on the website: [AEI](/aei).

## The four elements

URL: https://kabaido.ai/docs/platform/the-four-elements

Find the product that fits a need by its element, and know why the menu is grouped differently.

Why: People look for a product by the job it helps with, not by its name.
What: Sales, Logistics, Production and Marketing group the products by the part of the business they serve.
How: Use them on the website's Products menu and on the onboarding tiles to find what fits.

### The products in each element

| Element | Products | Also useful to |
| --- | --- | --- |
| Sales | [Sales Engineer](/docs/sales-engineer) and [Design Engineer](/docs/design-engineer) | [Service Centre](/docs/service-centre) and [Wizard](/docs/wizard) |
| Logistics | [Route](/docs/route), [Source](/docs/source) and [Stock](/docs/stock) |  |
| Production | [Service Centre](/docs/service-centre) and [Machinist](/docs/machinist) | [Stock](/docs/stock) |
| Marketing | [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |  |

An element is never a product: there is no product called Sales or Logistics. Each product has one element and at most one second.

### The menu groups are different

Inside the platform the menu lists areas, not products, each with its own icon, in the order Sales, Products, Operations and Growth. **New request** and **Search** sit above them, your **Stations** and your **Recents** below, and Settings is in the account menu at the foot. A short menu is one list; once it holds 7 areas or more each group carries its label, and a label folds its group away until you open it again.

## What changed at 1.0

URL: https://kabaido.ai/docs/platform/what-changed-at-1-0

Map what you knew of Kabaido before 1.0 onto how it works now.

Why: If you used Kabaido before 1.0, a few words and places have moved.
What: The release called Anthracite set the platform out as products, areas and parts, with one AI input and usage based plans.
How: Read the table, then follow the link for anything you use.

### At a glance

| Before | Now |
| --- | --- |
| Capabilities went by other names | Each is a [product](/docs/platform/products-areas-and-parts), switched on per workspace by need, on any plan. A design module, wizard module, machine module or service model is something you install inside one |
| AI boxes in several areas | [One AI input](/docs/platform/the-ai-interface) at `/app`, with links from other areas that write the prompt for you |
| A customer portal in every workspace | Commerce brings the [customer surface](/docs/commerce/the-customer-surface); a quote link still opens without it |
| Inventory came with other products | [Stock](/docs/stock) is a product of its own |
| Access set by role alone | [Role templates](/docs/getting-started/users-roles-and-permissions), areas per member and stations in the menu; the role still decides what someone can change |
| Allowances counted per action | [One usage pool](/docs/billing/how-usage-works) per workspace, never stated as a count, with no overage |
| The platform in several languages | English only; other languages return one at a time |

### The version

Every release carries a version in three parts, class, visible and background, such as `1.40.22`, the one you are on today. Class 1 is Anthracite and class 0 was the run up to it; a visible change raises the middle number and a background change the last. Settings then Organisation shows the **Platform version** you are on, and the [changelog](/docs/changelog) records each one.

> Nothing you made before 1.0 was deleted. Every existing workspace had its products switched on from the work already in it.

# Docs: Sales Engineer

## Sales Engineer

URL: https://kabaido.ai/docs/sales-engineer

Sales Engineer answers the technical customer request, from the enquiry arriving to the quote or order going back.

Sales Engineer answers the technical customer request, from the enquiry arriving to the quote or order going back.

It can read a request for quotation or a drawing, work out what the customer needs, match it against your catalogue, price it on your real costs and draft the branded reply on the original thread. With your customer's context and the engineering behind what you sell built into every answer.

Give your customers a considered answer within the hour, at any hour, and a quote that holds up when their engineer reads it.

When something is missing it asks a clarifying question and cites what it found, rather than guessing a specification.

Connect Gmail or Microsoft 365 and it works where your customers already write to you.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Sales Engineer reads a request typed, pasted or attached in the AI area, or arriving in a connected inbox, and sets out what the customer asked for with a source span behind every attribute. It matches each line to your catalogue records, prices it on your price list, special prices and quantity breaks, and drafts the quote or order. Through [the email agent](/docs/sales-engineer/the-email-agent) it classifies inbound mail as a request for quotation, a purchase order, a technical question or none, and drafts a branded reply threaded on the original message; review mode is the default, so every draft goes to an internal address until the organisation decides otherwise. It reaches what else the workspace has switched on, so a servicing line or a custom design comes into the same answer.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | an area in the menu |

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings Quotes, Orders and the Catalogue, with the AI reading requests, matching your catalogue and drafting the reply on the original thread.

Switched off: Your quotes, orders and catalogue stay exactly as they are and stay readable. Nothing new can be quoted from the catalogue until it is switched on again.

### Who uses it

- Internal Sales
- Technical Sales Engineer
- Applications Engineer
- Sales Engineer
- Estimator
- Customer Service Coordinator

### Two rules it keeps

- **Cite or abstain.** Every value carries the span of the request it was read from. A specification, tolerance, price or part number is never invented; a missing one becomes a question.
- **The numbers are calculated.** Fit scores, match bands and prices come from your schema, your catalogue and your pricing rules, so the same structured line against the same catalogue scores the same every time.

## Sending a request

URL: https://kabaido.ai/docs/sales-engineer/sending-a-request

Send a customer enquiry to the AI area as text, a file or a paste and get a structured answer back.

Why: An enquiry arrives in whatever form the customer had to hand, and retyping it is where figures change.
What: The one AI input at `/app` reads it as it arrived and returns the lines, the matches and a draft.
How: Pick what you are sending, paste or attach it and send.

### Send one

1. Open `/app`, the one AI input in the platform.
2. Choose what your customer sent: **Request** (an enquiry to price, an RFQ or a drawing), **Order** (a purchase order to raise) or **Question** (answered with its sources). There is no automatic mode.
3. Optionally pin a customer with the customer chip, so the answer uses what you know about them, such as their order history. See [Customer context](/docs/parts/customer-context).
4. Type or paste the enquiry, attach files or drop them anywhere on the conversation, then press **Send message**.


### What you can attach

| File | How it is read |
| --- | --- |
| PDF | Text pages as text; scanned pages by vision. |
| PNG, JPEG, WebP, GIF | By vision, as a drawing or a photograph. |
| XLSX, XLS, CSV | As a table, cell by cell. |
| DOCX, TXT, Markdown | As text. |
| EML, Outlook MSG | As the email, with the documents inside it read too. |
| DXF | As a measured summary: extents, layers and the text on the drawing. A long drawing is cut short and the summary says so. |

> The upload limit is 4 MB per file. Split a larger document or send the relevant pages on their own.

3D models (STEP, IGES, SLDPRT, STL and similar) cannot be attached: Kabaido reads 2D drawings. Export a DXF or a PDF drawing, or state the sizes in the message. One arriving by email is skipped with a note saying why.

Scanned pages are read up to a cap per request, lower on the free plan than on a paid one. Pages past the cap are skipped with a warning, never dropped silently.

### The usage bar

A thin bar sits at the top right of the input. Hover, focus or tap it to see how much of the month is used, the daily budget if one is set and the reset date. See [Usage and what draws on it](/docs/sales-engineer/usage-and-what-draws-on-it).

### Other ways a request arrives

- A connected inbox: [the email agent](/docs/sales-engineer/the-email-agent) turns detected enquiries into requests.
- An [inbound endpoint](/docs/api/inbound-endpoints) any system can post enquiry text to.
- The [REST API](/docs/api/the-rest-api): `POST /api/v1/requests`.
- An AI assistant over [MCP](/docs/api/mcp), where `create_request` opens a thread your team sees.

Every one lands as a chat under **Recents** in the menu. It works before you import anything: with no catalogue you still get the structured lines back, and matching switches on once your products are in.

## How requests are structured

URL: https://kabaido.ai/docs/sales-engineer/how-requests-are-structured

Read the structured request: typed lines, normalised units and a citation behind every value.

Why: A figure you cannot trace back to the customer's words has to be checked by hand, which is the work this removes.
What: Each request becomes a **Structured request** card: one row per thing asked for, every attribute cited.
How: Tap or click any value on the card to see the original text it was read from.


### What a line carries

| Part | What it is |
| --- | --- |
| Description | What the customer asked for, in their words. |
| Quantity and unit | As stated. One nobody gave is assumed as one off and marked **assumed**, or shown as **not stated** when you ask for it instead. |
| Attributes | Material, diameter, coating, tolerance and the rest, each in its own typed field. |
| Citation | The span of the request each value came from. |
| Not stated | The parameters that specify this kind of product, or the inputs a matched service needs, that the request left open. |

### Normalised, with the original kept

The same size arrives as 12mm, 12 dia, Ø12 or 1/2in. The typed field holds one value in one unit so lines compare and formulas can read them, and the customer's own wording is kept one tap away.

### Missing means a question

A value the request does not state stays empty. Where your order history, the customer's details or an engineering norm settles it, Kabaido fills it and marks it **assumed** with its basis; a specification, tolerance, price or part number is never assumed. See [Clarifications](/docs/sales-engineer/clarifications).

### The whole specification

Under each line, **Not stated** lists the parameters its kind of product is specified by that the request left open, as far as your catalogue schema scores them. You can tell a complete line from a thin one before the quote goes out.

> The structured card needs no catalogue: it is what you get on day one. See [Schemas and fields](/docs/catalog/schemas-and-fields) for the parameters it reads against once you have one.

## Working with matches

URL: https://kabaido.ai/docs/sales-engineer/working-with-matches

Read how a line is matched to your catalogue, and overrule the match when you disagree.

Why: A match you cannot explain is a match you cannot defend to the customer's engineer.
What: Each line is scored against your products field by field, out of 100, and banded by fixed thresholds.
How: Read the fit and its chips on the line, pick another candidate or press **Challenge this match**.


### What a line resolves to

A part number the request quotes locks to that product. Work on the customer's own item, or a line whose stated parameters fit exactly one of your services, goes to that service. Anything else goes to your catalogue where you stock that kind of product; where you do not, to a designed product you have saved, then a service, then a design module that fits. A line that matches nothing keeps its structure; see [Made to spec](/docs/sales-engineer/made-to-spec).

### The fit

Each schema field carries a weight, and the fit is the weighted average of how well the product meets each stated field. Exact counts 100 per cent of the field's weight, within tolerance 85, an accepted alternative 60, a value the product does not state 35 and a miss 0. A miss on a stated hard field rules the product out.

| Chip | Means |
| --- | --- |
| Green | Exact on that field. |
| Blue | Within tolerance. |
| Amber | An accepted alternative, a longer size supplied for a shorter one, or an assumed value. |
| Red | A miss. |
| Grey | The product does not state it. |

### The bands

| Band | When | What you see |
| --- | --- | --- |
| Matched | Fit 86 or more and 8 points clear of the next | **Matched product**, with the alternatives a click away |
| Review | Fit 60 or more, no clear winner | **Review matches**: the top three to pick from |
| Closest | Fit 40 or more | **Closest match**, unpriced, with where it differs |
| None | Below 40 | The line stays structured and unpriced |

A substituted size, or a match carried mostly by assumptions or contradicting one, never selects itself: it drops to review so a person confirms it.

### Tolerances and equivalents

A number matches within the tolerance set on its schema field, or 5 per cent where none is set. A field marked nearest above takes the next size up within a 20 per cent overshoot. Known equivalents, such as TiAlN and AlTiN, score as alternatives and show amber, never as exact.

### Where the AI touches matching

Scores and bands are calculation. The model only reorders candidates inside the review band, where a person picks anyway.

### Overrule a match

1. In **Review matches**, pick the candidate you want. The selection is saved on the request.
2. On a matched line you disagree with, press **Challenge this match**: the heavier model reranks the candidates and a fresh **Review matches** card is added to the thread.

## Clarifications

URL: https://kabaido.ai/docs/sales-engineer/clarifications

Answer what a request left out, see what was assumed, and have the line resolved again.

Why: A silent default reads as confident, nobody re-checks it and the customer finds the mistake.
What: Kabaido leaves a missing value empty and asks, on the line it belongs to.
How: Answer on the line or in the composer, and the line is resolved again with your answer.


### Answer one

1. Find the **Not stated** list on the line, or the **Clarification** card in the answer.
2. Press **Fill these in** (**Fill this in** for one) and answer what you know. Anything left blank stays open.
3. Press **Send answers** or **Resolve this line again**, or simply reply in the composer.

You can answer for the customer: the buyer said it on the phone, or it is obvious from their last order. What matters is that the answer is recorded rather than guessed.

### What is assumed, and how you see it

Where your order history, the customer's details or a published engineering norm settles a parameter, Kabaido fills it and marks it **assumed** with the basis it stood on. A quantity nobody stated is set to one off so the line can be priced.

- An assumed value shows as a dashed amber chip and is listed again at the end of the answer.
- Press the chip to change the value, or **Ask me instead** to turn it back into a question.
- A specification, tolerance, price or part number is never assumed. A missing one is always a question.

### When to leave one open

A clarification is not a blocker. The line stays on the card with everything that was stated, and on the draft it is marked **Needs information**. You can create the quote and price that line by hand.

> Your answers merge into the same request and the result is added to the thread as new cards; the earlier cards are never rewritten.

## Quotes and orders from a request

URL: https://kabaido.ai/docs/sales-engineer/quotes-and-orders-from-a-request

Turn a reviewed request into a real quote or order, with its lines, prices and customer carried across.

Why: Retyping a request into a quote is where a figure changes and nobody notices.
What: The answer ends in a **Quote draft** or an **Order draft** card that creates the real record.
How: Check the draft, then press **Create quote** or **Create order**.


### Create a quote

1. Send the enquiry in **Request** mode at `/app`.
2. Read the **Quote draft**: each line is marked **Ready** or **Needs information**, with its unit price and quantity.
3. Check the customer on the card, then press **Create quote**. The quote opens in `/app/quotes` and the thread links to it.

### What carries across

- The description, quantity and unit of each line.
- The matched product, the configured design or the service.
- The unit price from your own rules: the price list, special prices and breaks for that customer on a catalogue line, your rates on a designed line and your service book on a service. It is never a figure the AI produced.
- The customer, and a link from the quote back to the request.

### Lines that are not ready

A line with an open question, no match or no price comes across as an unpriced **Manual** line to finish in the editor. A line whose quantity reads **not stated** is left out of the draft's total, and comes across the same way with its description saying so; a quantity assumed as one off is priced and marked **assumed**. A service line the service rejected is left off. Nothing is filled in to close the gap.

### Create an order

1. Send the purchase order in **Order** mode. Lines are matched and checked against the quote they came from, shown as **From quote**.
2. Where quantities or assumed values were not stated, tick the confirmation on the card.
3. Press **Create order**. It opens in `/app/orders`.

> Created records are added to the thread, never written over it, so the conversation stays as the record of how the quote or order was reached.

## Made to spec

URL: https://kabaido.ai/docs/sales-engineer/made-to-spec

Handle a request with no catalogue match: set out, handed to the right product or priced by you.

Why: Much of what an industrial customer asks for is made to their drawing, and there is no part number to match.
What: A line read as made to specification keeps its structure and goes to whatever in the workspace can answer it.
How: Kabaido routes each line on its own; where it could not answer one, you hand it over or price it yourself.

### Decided per line

You never declare a request a design job before sending it. A mixed enquiry of stock items and one fabricated part is read as exactly that, and each line goes where it belongs.

| The line is | What happens | Needs |
| --- | --- | --- |
| Made to a specification a design module covers | It is configured and priced on your rates inside the same answer, for a few lines per request. | Design Engineer, with that design module installed |
| Work on the customer's own item | It is priced on your service book, with your rules applied. | Service Centre, with the service set up |
| Close to a service but not close enough | The closest services are named and nothing is priced. Say which one it is, or price it on the quote. | Service Centre |
| None of these | It is set out, sizes, materials and quantities cited, ready for you to price. | Nothing more |

### Hand a line to the Design Engineer

1. On a line read as made to specification, press **Design this line**.
2. Or, on the **Made to order** card, press **Design this with the Design Engineer** for the whole request.
3. The design answers in the same conversation, and is also stored as its own design thread you can reopen.

A drawing sent into a design thread is transcribed first, into the dimensions and notes printed on it, and the transcription is shown in the thread beside what was configured from it. Check it against the drawing.

### Price it yourself

The **Made to order** card says there is no catalogue part to match: nothing is priced for you and nothing is guessed. Press **Create quote** on the **Quote draft** and the lines come across with their descriptions, sizes and quantities for you to price in `/app/quotes`. A line you add there by hand is a **Manual** line.

> If part of the request is standard stock you supply, [import it](/docs/catalog/importing-products) and those lines match from then on.

## The email agent

URL: https://kabaido.ai/docs/sales-engineer/the-email-agent

Connect a Gmail or Microsoft 365 inbox and let Sales Engineer answer the enquiries that already arrive there.

Why: Your customers already write to an inbox, and every enquiry copied out of it is time lost.
What: The agent reads new mail, recognises requests, purchase orders and questions, and runs them as requests.
How: Connect the inbox in Settings then Integrations, choose how it answers, and watch its activity.

### Connect an inbox

1. Open `/app/settings/integrations` and the **Email agent** entry. You need the admin role.
2. Press **Connect Gmail** or **Connect Microsoft 365** and approve the access with the provider.
3. You land on the inbox page at `/app/settings/integrations/email/[inboxId]`, where its settings and activity live.

The agent reads only mail that arrives after you connect, and never deletes or moves anything.

### What it does

- Checks for new mail every few minutes; **Sync now** checks at once.
- Classifies each message as **RFQ**, **PO**, **Question** or **No action**. Its own sends, bounces and auto replies are never answered.
- Runs a recognised enquiry through the same pipeline as the AI area, attachments included, as a request under Recents in the menu.
- Drafts the reply: the quote with its PDF, a clarifying question, a cited answer or an order acknowledgement. It never commits an order itself.

### How this inbox is handled

| Setting | Choices |
| --- | --- |
| When an enquiry is recognised | **Answer it** runs the request at once. **Prepare it and wait** builds the request with its attachments, marked unseen, and nothing runs until you send it. |
| Reply mode | **Review first**, the default, sends every draft to the **Review address**. **Direct** replies to the customer from the inbox. |
| Sender name and signature | Shown on replies, above your organisation's branding. |
| Filters | Only or never these senders and domains, and subjects to skip. |

Switch to **Direct** once the drafts are consistently right. Pausing the inbox stops all reading and replying; mail that arrives meanwhile is picked up when you resume.

### Activity

The inbox page lists every email the agent has seen, with its kind, its status and the usage it drew. Filtered mail is listed too, with **Process** to run it by hand. No email is processed twice.

### Usage

Recognising and classifying mail draws nothing. A run draws the same as it would in the AI area, and a drafted reply a little more. A prepared enquiry draws nothing until you send it.

## Usage and what draws on it

URL: https://kabaido.ai/docs/sales-engineer/usage-and-what-draws-on-it

Know what draws on your plan's one pool of usage, what never does and what happens when it runs out.

Why: You should be able to send a request without checking a price list first.
What: Every plan holds one pool of usage, shared by the AI and the platform's activity.
How: Watch the bar at the AI input; the detail lives in Settings then Billing.


### What draws on it

| Work | Draws |
| --- | --- |
| Reading and resolving a request, per line | Most of it. A line priced on a service or configured draws more than a catalogue line. |
| Scanned pages and drawings read by vision | More than text. |
| A harder request answered by the heavier model | More again. |
| A reply drafted by the email agent | A little, on top of the run. |
| Some records a person creates or changes, such as a supplier, a stock movement or a production job | A very small amount. |
| A wizard run, or an exported design document | A very small amount. |

A line draws on the pool when it is first resolved. A follow up turn draws only for the lines that are new against what the thread already resolved.

### What never draws on it

Browsing, searching, filtering and reading, reopening a thread, rendering a quote PDF, receiving a notification and a customer reading their own records.

### Seeing it

The bar at the top right of the AI input opens a card with the share of the month used in plain words, what has used it, today's budget if one is set and the reset date. You never see a unit count.

### The pool by plan

- Ultra holds three and a half times the usage of Pro, and Max eight and a half times.
- A paid plan's pool resets on the billing date and does not roll over.
- The free plan's allowance is for the life of the account and does not refresh.
- An owner can set a [daily budget](/docs/billing/daily-budgets) so one busy day cannot take the month.

> There is no overage. When the pool runs out, AI answers pause and everything you do by hand carries on until the reset or an upgrade, which refreshes usage straight away.

# Docs: Design Engineer

## Design Engineer

URL: https://kabaido.ai/docs/design-engineer

Design Engineer turns a custom enquiry into a configured, priced and drawn product.

Design Engineer turns a custom enquiry into a configured, priced and drawn product.

It can configure the part in 3D, price it on your real costs, produce the model and drawing files and put the whole thing on a quote. Change a parameter and the geometry, the price, the cost and the lead time move with it.

Give your customers a bespoke answer in minutes rather than days, with a drawing to approve and a price that stands up.

Anyone in the sales office can drive it, or the AI can, from the customer's own words and the drawing they attached.

Design modules cover soft jaws, gaskets, plastics cut to size, balustrades, PCD saw blades, PCD profile cutters, PCD shank tools and solid carbide endmills. New ones are built to order for what you make.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

A CAD workbench where each design module carries its own parameters, geometry, rules and price lines. The output is a 3D model, a specification PDF, production files and a designed product the Sales Engineer can put on a quote. Checks stop an impossible combination before anything is exported. Stock lines are held per design module with whether each needs preparing, and a counted line is written to the same stock ledger the Stock product shows.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Design](/docs/areas/design) | `/app/design` | a full screen workbench |

It adds to [Stock](/docs/areas/stock) when the product that brings that area is on too.

Works with [Stock](/docs/stock) and [Commerce](/docs/commerce). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Design workbench with your design modules, custom lines on quotes and orders, and the AI configuring a part from the customer's own words.

Switched off: Saved designs stay readable and every quote that carries one is unchanged. No new design can be configured until it is switched on again.

### Who uses it

- Design Engineer
- Applications Engineer
- Technical Sales
- Estimator
- Internal Sales

### Two ways to drive it

- **By hand**: open `/app/design` and change a parameter. Configuring by hand draws no usage.
- **By the AI**: in the [AI interface](/docs/platform/the-ai-interface) at `/app`, a request line that reads as work to be made is configured in the design module that fits it, priced and drawn inside the answer. **Open in the workbench** takes the result to `/app/design`. On a line read as made to specification, **Design this line** opens a design conversation under that line.

## The workbench

URL: https://kabaido.ai/docs/design-engineer/the-workbench

Open a design module, configure a part, keep it as a file and find the four views.

Why: A bespoke part needs its geometry, its checks and its price worked out together.
What: One full screen workbench per design module: parameters, the model, your files and your rates.
How: Open `/app/design`; it reopens the work you had open, so you pick up where you stopped.

Screenshot of /app/design/balustrades-handrails: The Design workbench on the balustrade design module: the parameters, the 3D model of the run and the price with its working at the preset's example rates.

### Where it opens

1. The design you had open last, if its design module is still on.
2. Otherwise the newest design in the workspace.
3. Otherwise a fresh file on the first design module that is on.
4. With no design module on, a screen that points you at [presets](/docs/parts/presets) to switch one on.

`/app/design/<design module>?design=new` always opens a blank file.

### The views

| View | Where | What it holds |
| --- | --- | --- |
| Parameters | Left | The inputs in their groups, with ranges and units. Values marked **Worked out for you** follow from the others. |
| Model | Centre | The part, rebuilt in your browser as you type. **Give the model the whole width** hides the parameters. |
| Files | Toolbar | **Switch design** lists this design module's files, newest first, with **New**, **Rename**, **Duplicate** and **Delete**. |
| Rates and stock | Toolbar | `/app/design/<design module>/settings`: what each price line charges and the stock you hold. |

The rail on the right opens one panel at a time: **Price and working**, **Materials and cutting list**, **Checks and compliance**, **Documents and exports** and **Save and reopen**. For the engineer role and above, the rail also carries **Ask about this design**, which opens `/app` with the design module and the values on screen.

### Autosave and files

1. Change any parameter. The first change writes a **Draft**, and the save state beside the file name shows **Saving** then **Saved**.
2. Open **Save and reopen**, name the configuration and choose **Save as a designed product**. The Sales Engineer can match request lines against it from then on.
3. If a colleague saved a newer version first, autosave stops and offers **Open theirs** or **Keep mine as a copy**. Nothing is merged silently.

The price is worked out again on the server every time a design saves. Saving needs the engineer role or above; anyone else can configure and look, and nothing they change is kept.

### Plan allowances

Drafts are free and unlimited. Named designs and exports are capped by plan, and an export also draws on your usage.

| Plan | Saved designs | Exports a month |
| --- | --- | --- |
| Free | 5 | 10 |
| Pro | 250 | 250 |
| Ultra | 2,500 | 1,000 |
| Max | 25,000 | Fair use |

Interactive example: The workbench drawn by the real engine: a soft jaw set's parameters, drawing and price.

## The design modules

URL: https://kabaido.ai/docs/design-engineer/the-design-modules

Know what each design module installed today configures, what it produces and which preset brings it.

Why: Each trade prices its custom work differently, so each needs its own parameters and rules.
What: The design modules built today, each read from the same registry the platform and the website use.
How: Switch one on by turning on its preset in `/app/settings/presets`; it then appears in the workbench's **Switch design module** list.

### Solid carbide endmills

Special endmills and form cutters ground from rod, priced pass by pass and drawn.

**Out**: Price with grinding pass by pass, Tool drawing, Rod and grinding schedule, Spec sheet PDF and STEP model. **Arrives with** the Solid round tools preset. [On the website](/design-engineer/solid-carbide-endmills).

### PCD profile cutters

Diamond tipped profile and jointing cutters on steel bodies, with knife form, disc yield and body billet priced.

**Out**: Price from your own rates, Knife form DXF, Knife and disc schedule, Spec sheet PDF and STEP model. **Arrives with** the PCD and diamond tooling preset. [On the website](/design-engineer/pcd-profile-cutter).

### PCD shank tools

PCD tipped routers, end mills, drills and reamers, tips nested on your discs.

**Out**: Customer drawing, Nest DXF, Cutting list, Spec sheet and STEP. **Arrives with** the PCD and diamond tooling preset. [On the website](/design-engineer/pcd-shank-tool).

### PCD saw blades

Diamond tipped circular saw blades built tooth by tooth, with tips, discs, braze and body blank priced.

**Out**: Price from your own rates, Body blank DXF, Tip and disc schedule, Spec sheet PDF and STEP model. **Arrives with** the Saw blades and PCD and diamond tooling presets. [On the website](/design-engineer/pcd-saw-blade).

### Balustrades and handrails

Balustrade and handrail runs set out as a fabricator quotes them: level runs, corners, stair rakes and landings.

**Out**: Price from your own rates, Cutting list, Glass schedule, Drawn quote, DXF elevation and Compliance checks. **Arrives with** the Balustrades and architectural metalwork preset. [On the website](/design-engineer/balustrades-handrails).

### Soft jaws

Machinable soft jaw sets for wedge type lathe chucks, with the grip pocket cut to the workpiece.

**Out**: Price from your own rates, Dimensioned drawing, Spec sheet PDF, Material list and STEP and STL models. **Arrives with** the Toolholding and workholding preset. [On the website](/design-engineer/soft-jaws).

### Gaskets

Full face, ring, rectangular and drawn gaskets cut from sheet, priced with a cut ready profile.

**Out**: Price from your own rates, Cut ready DXF, Sheet take off and Spec sheet PDF. **Arrives with** the Gaskets and sealing preset. [On the website](/design-engineer/gaskets).

### Cut to size plastics

Plastic sheet, rod and tube cut to size from stock, or a part cut to an outline you draw.

**Out**: Price from your own rates, Cutting list, DXF outline, Spec sheet PDF and Stock match with offcut. **Arrives with** the Cut-to-size plastics preset. [On the website](/design-engineer/plastics-cut-to-size).

> Every design module prices from example rates until you set your own, and says so on the price. See [Rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

## Quote a special endmill

URL: https://kabaido.ai/docs/design-engineer/quote-a-special-endmill

Take a special endmill enquiry from the email it arrived in to a quote with the designed tool on it.

Why: A special endmill quote needs the rod, the grinding and the coating worked out before anyone can reply.
What: One path from the enquiry to a quote, with the tool configured, checked and drawn in the solid carbide endmill design module.
How: Send the enquiry at `/app`, check what was read, then create the quote from the draft.

### Before you start

- The [solid carbide endmill](/design-engineer/solid-carbide-endmills) design module arrives with the **Solid round tools** or **Solid carbide tool making** preset. If it is not in the workbench's **Switch design module** list, turn one on in `/app/settings/presets`.
- It runs on every plan, Free included. Saved designs and exports are capped by plan: see [The workbench](/docs/design-engineer/the-workbench).
- Until you set your own rates it prices from example rates and says so on the price. See [Rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

### Send the enquiry

1. Open `/app` and choose **Request**. Paste the enquiry, or attach the email as EML or MSG, a PDF drawing or a DXF of the form.
2. Press **Send message**. With an inbox connected, [the email agent](/docs/sales-engineer/the-email-agent) turns an enquiry that arrives there into the same request.

### What AEI reads and cites

Each line is set out with its sizes, grade, coating and quantity. A line read as a special endmill is configured in the design module inside the same answer; on any other line read as made to specification, press **Design this line**.

- **AI set** beside a value opens why it was set, with the words from the enquiry behind it.
- **From the DXF** marks a value taken from an attached form drawing.
- Values read off a drawing image are listed under **Read off the drawing image** for you to confirm.
- A value the enquiry does not state shows as the design module's default. If nothing can be grounded, nothing is configured and the card says so.

### Check the design in the answer

The **Design result** card shows the tool as a drawing and a 3D model, the **Configured price** with **The working behind each line**, and the checks.

- **Stock that covers this size** lists the rod from your stock that can make the tool, matched on the largest ground diameter, with its yield. **Nothing in stock covers this size** means no rod on your list is big enough.
- The grinding is priced pass by pass: flute grinding, gashing and end teeth, relief and any corner or form, then the coating.
- A blocking issue is a tool that cannot be made as configured, such as a corner radius larger than half the cutting diameter or a form longer than the length of cut. It stops every export until it is fixed.

### Open it in the workbench

1. Press **Open in the workbench**. The tool opens at `/app/design/solid-carbide-endmills` on the values from the answer.
2. Change any parameter and the model, the checks and the price follow as you type. A blocking check shows under **Resolve before exporting**.
3. Open **Materials and cutting list** to see the rod: each item reads **Covers the size** or **Too small for this size**. Load your own rod first, as [Stock matching](/docs/design-engineer/stock-pools-and-matching) sets out.
4. Name it and choose **Save as a designed product** so the Sales Engineer can quote the next enquiry for the same tool from it. Saving needs the engineer role.

### The drawing and the spec sheet

On the card, **Spec sheet** and **Cutting list** produce the documents straight away. In the workbench, **Documents and exports** adds the customer drawing, the DXF, STL, GLB and STEP.

| Output | What it holds |
| --- | --- |
| Customer drawing | One A4 landscape sheet: the side view at a true scale with every length, diameter and fit, section A-A through the flutes, the land and the end tooth enlarged, three views of the solid, the tool data, the customer with their own prices at each quantity, the notes and a title block with your logo and brand colour. Choose a works copy for the grinding floor: the rod and the grinding time in place of the prices. |
| Spec sheet PDF | The dimensioned tool drawing, every parameter, the price and the assumptions. |
| Cutting list CSV | The rod and each grinding pass, for the grinding floor. |
| DXF and STEP | The profile as line work, and the tool as solid geometry for CAD. |

The customer drawing asks for the customer, their part number and reference, the revision, the quantities to price and the cutting diameter tolerance. The prices are the design module's own at each quantity with that customer's account terms applied, the same figure a quote for them would carry. The logo, address, company number and brand colour come from **Settings**, **Organisation**. A cutting diameter tolerance left empty is printed as to be agreed, never guessed.

> A document uses one of your plan's monthly exports and a little of your monthly usage. Saving costs nothing. More in [Drawings and exports](/docs/design-engineer/drawing-engines-and-renderings).

### Put it on the quote

1. Read the **Quote draft** at the foot of the answer. The endmill is a **Design configured** line priced on your rates; a line with an open question reads **Needs information**.
2. Check the customer, then press **Create quote**. The quote opens in `/app/quotes` with the design and its price carried across.

The price is never a figure the AI produced: it comes from the design module's rates. See [Quotes and orders from a request](/docs/sales-engineer/quotes-and-orders-from-a-request).

> The design module covers endmills and form cutters. Solid carbide drills, reamers and countersinks are not built yet.

## How a design module is built

URL: https://kabaido.ai/docs/design-engineer/building-a-configurator

Know the parts of a design module, which of them you change and which are built to order.

Why: A price you can defend has to come from rules and rates you can read.
What: Every design module is data: parameters, a take-off, price lines, checks and a stock match.
How: Read the pieces here; change your rates and stock in **Rates and stock**.

### The pieces

| Piece | What it does |
| --- | --- |
| Parameters | Number, select, yes or no, text and sketch inputs, in groups, with a unit, a range and a default. Choosing an option can fill in others: a chuck fills in the jaw blank. |
| Take-off | Counts what the part needs: cuts, lengths, areas, panels, fixings. It becomes the cutting list. |
| Price lines | Each line multiplies a quantity the take-off counted by one of your rates, so every figure shows its working. |
| Checks | Decision tables that return a **block** or a **warning** in plain words. |
| Stock match | Which of your stock items the part can be cut or made from. See [Stock matching](/docs/design-engineer/stock-pools-and-matching). |

### Checks: block and warning

A block is work that cannot be made as configured: it shows under **Resolve before exporting** and stops every export until it is fixed. A warning shows under **Worth checking** and changes nothing.

### What you change, and what you do not

- **Yours**: the rates behind each price line, the materials and multipliers, your stock list and, where shipped, the example labels on the limits.
- **Built by Kabaido**: the parameters, the take-off, the price lines and the checks. A change to those, or a new design module, is [built to order](/docs/design-engineer/custom-modules-and-the-roadmap).

> The formula builder with a test bench, where you write parameters, formulas and rules yourself, is how Service Centre builds a [service model](/docs/service-centre/service-models-and-workflow-types). Design modules do not use it.

Interactive example: A balustrade priced line by line, each line with its working, on the preset's example rates.

## Geometry and price

URL: https://kabaido.ai/docs/design-engineer/geometry-pricing

Know what drives a design module's price from the shape of the part, and what does not.

Why: Custom parts are priced by their shape: cut length, area, material used.
What: The shape comes from the parameters and any outline you sketch, never from a measured model.
How: Set the parameters or draw the outline; the take-off measures it and the price lines read the take-off.

> There is no upload that prices a part from a 3D model. A DXF can become a sketch outline you see and edit, and a drawing on a request can fill in parameters you can check; the price always comes from the parameters. No solid or mesh you send is ever measured.

### What the price reads

The take-off works out the quantities from the parameters: a gasket's cut length and face area, a balustrade's posts and bars, a blade's tips and discs. The price lines multiply those by your rates.

### Sketching an outline

Every design module except Soft jaws and PCD shank tools has a sketch parameter: a closed outline with holes, or a run set out on plan.

1. Open the sketch parameter and choose **Draw the outline**, or start from a **Rectangle** or a **Circle**.
2. Or, on an outline, choose **Import a DXF**: closed polylines become the outline and circles become holes. **Scale to width** fixes a file drawn in other units.
3. Choose **Use this outline** (**Use this plan** on a balustrade run). The shape is now a parameter, and the take-off measures it like any other.

### A drawing attached to a request

In the AI interface, a drawing attached to a request is transcribed first: the dimensions, tolerances and notes printed on it. A line work file is read as a summary of its measurements. What was read shows in the thread, and every value the configure pass sets cites text you can check.

> Nothing is measured off the picture. A figure that cannot be read is left out, not guessed.

## Stock matching

URL: https://kabaido.ai/docs/design-engineer/stock-pools-and-matching

Load the stock a design module cuts from and read which item covers a configuration.

Why: A custom part is made from the next size up, so the stock it comes from decides the waste.
What: A stock list per design module, matched against every configuration as you type.
How: Load your list in **Rates and stock**, then read **Materials and cutting list** in the workbench.

### Load your stock

1. Open `/app/design/<design module>/settings` and choose the **Stock** tab.
2. Choose **Add an item**, or **Import a CSV** (**Download template CSV** gives the columns). A code already in the list is updated in place.
3. Fill the **Matching** values the design module reads. A value left empty shows **Not set**, and a rule that reads it cannot match that row.
4. Remove the shipped examples with **Remove the example rows** once your own list is in.

### How a match is decided

| Rule | Meaning |
| --- | --- |
| Filters | Must equal exactly: material, form or section. |
| Exact sizes | Must equal numerically, such as a thickness that comes from stock. |
| Envelope | Must cover the part: the blank at least as big as what is made from it. |

Each item then reads **Covers the size** or **Too small for this size**, with the share of the stock the part uses. The [solid carbide endmill](/design-engineer/solid-carbide-endmills) design module matches rod on the largest ground diameter, so a stepped tool buys a blank that can make it.

> Stock prices record what you pay for the material. They do not price the quote: the rates do. A PCD shank tool line is the exception: its bar and discs are priced at the cost on the stock rows it matches, and it reserves the counted ones when the order is created. Every other design module reserves nothing and takes nothing off the stock list.

To count what you hold and connect a line to a machine, see [Rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

## Rates, stock and the machine bridge

URL: https://kabaido.ai/docs/design-engineer/stock-modes

Set your own rates, count the stock behind a design module and let an order raise the machine work.

Why: A shipped design module prices from example rates, not yours.
What: The **Rates and stock** view: your rates, your stock, counted lines and machine connections.
How: Open `/app/design/<design module>/settings`; engineers, admins and owners can change it.

### Set your rates

1. Open the **Rates** tab. While the example rates apply, **Set your rates** in the workbench toolbar goes straight there.
2. Change the rates under **What each price line charges** and **Materials and multipliers**. Each shows its unit, and a value outside its range is refused where you type it.
3. Check **What will be written**, then choose the save button, which counts your changes (**Save 2 changes**). Every quote from then on uses them.

Any save here gives the workspace its own copy of the design module. Saving a rate also takes the example label off the price.

### Counted stock and preparation

Rates and rules is the default and needs nothing more. In the **Stock mode** panel below the tabs, a line can instead be **Counted stock** with a **Warn below** threshold, and **Prepped, ready to use** or **Requires preparation**. A counted line at or under its threshold shows **Low stock**. The controls unlock once the workspace has its own copy.

A counted line is written to the one stock ledger for every workspace. With the [Stock](/docs/stock) product on it appears in `/app/stock` as a line from **Design**, and every change to its count is a movement.

### Connecting a machine module

A line that **Requires preparation** can connect to the machine module that makes it (**Arcline cuts it**, **Wire EDM erodes it**, **CNC Milling machines it**), when that machine module is on and the design module's take-off declares the job.

| Design module | Connects to | What it raises |
| --- | --- | --- |
| PCD saw blades | Arcline | The blade body blank |
| PCD saw blades | Wire EDM | The PCD tip blanks |
| PCD profile cutters | Wire EDM | The PCD knife blanks |
| PCD profile cutters | CNC Milling | The machined cutter body |
| PCD shank tools | Wire EDM | The PCD tip blanks, when they are cut by wire |
| PCD shank tools | CNC Milling | The turned, milled and ground shank |
| PCD shank tools | Machinist, as a manual job | The braze, raised for someone to do and tick off |

An Arcline connection asks for the material, the sheet thickness and the **Machine rate £/h**, reads your cut chart and writes the body cutting rate, with the working shown. Wire EDM and CNC Milling connections raise the work and do not change the price.

### When the order lands

1. An order is created: from an accepted quote, from a customer's purchase order read in the AI interface or from a Commerce website.
2. For each designed line, the take-off declares its production jobs and each goes to its connected machine module.
3. The machine order arrives queued in that machine module's **Orders** view ([Arcline](/docs/machinist/arcline), [Wire EDM](/docs/machinist/wire-edm) or [CNC Milling](/docs/machinist/cnc-milling)), with a note naming the order it came from. A retried order never queues the same work twice.

> A PCD shank tool line reserves its counted bar and discs when the order is created and consumes them when its production is done or the order is fulfilled. For every other design module nothing is reserved and nothing is taken off when an order is placed: the count changes only when someone edits it or records a movement against the line.

## Worked examples, revisions and resets

URL: https://kabaido.ai/docs/design-engineer/test-bench-and-versioning

Change a live design module's rates safely and explain any saved price later.

Why: A rate change affects every quote raised from that moment on.
What: Shipped worked examples, file revisions and a reset to the shipped preset.
How: Save rates in **Rates and stock**; reset from its **Going live** tab.

### Worked examples

Every shipped design module carries worked examples: fixed inputs with the price they must produce at the shipped rates. Kabaido's test suite runs them against the shipped rates.

They describe the shipped rates only, so saving a rate of your own drops them. From then on the live price, with its working on every line, is the check.

### Saved designs keep their price

- Each save stores the parameters and the price worked out on the server at that moment.
- Each file carries a revision. A save made from an older revision is reported as a conflict, never merged.
- Changing your rates later does not change a design already saved.

### Going live

Where a design module ships example limits and tables, they are labelled as examples wherever a customer could see them. Turn on **These limits and tables are ours** once they match your engineering. It changes labelling only: no limit, check or price moves.

### Back to the shipped preset

1. Open the **Going live** tab and find **Back to the shipped preset**.
2. Choose **Reset** and confirm. Your rates, stock and limits return to the shipped values; saved designs are kept.

> A reset cannot be undone.

## Drawings and exports

URL: https://kabaido.ai/docs/design-engineer/drawing-engines-and-renderings

Get the drawing, the specification and the production files out of a configured part.

Why: A buyer approves a picture of the part far faster than a paragraph about it.
What: A dimensioned drawing and files made from the same numbers that priced the part.
How: Open **Documents and exports** in the workbench rail and choose **Download** on a format.

### One set of numbers

Where a design module draws a dimensioned elevation on its PDF, the elevation is built from the same profile as its DXF. The 3D model is built in your browser from the parameters on screen. Both come from the values that priced the part.

### The formats

| Export | What it is |
| --- | --- |
| Specification and quote PDF | The dimensioned elevation, every parameter, the price and the assumptions. |
| Cutting list CSV | Every cut, panel and fixing with its size and quantity, for the workshop. |
| DXF | The elevation as line work on named layers. |
| STL | Mesh for viewing and printing. |
| GLB | Mesh for the web and for sharing. |
| STEP | Solid geometry for CAD. |

> Every export carries its configuration id and is built from the same values. The STEP is written from the design module's own solid geometry, and the DXF from its 2D profile.

### Before you export

- A blocking check stops every export until it is resolved.
- Each export draws on your usage and counts against the plan's monthly export allowance (see [The workbench](/docs/design-engineer/the-workbench)).
- Configuring and looking draw nothing.

With [Commerce](/docs/commerce) on, a signed in customer sees their own saved designs with the parameters and the price, never the breakdown, and can choose **Ask for a quote**.

## Custom design modules and the roadmap

URL: https://kabaido.ai/docs/design-engineer/custom-modules-and-the-roadmap

Ask for a design module Kabaido has not built yet, from the roadmap or from scratch.

Why: Your range may not match any design module that exists today.
What: Roadmap entries listed as built to order presets, and a custom build for anything else.
How: Ask from `/app/settings/presets`; a scoping call works out the parameters, the drawing and the pricing.

### The roadmap

These are design modules Kabaido has decided to build and has not built yet. Each shows in the presets list with a **Built to order** badge and installs nothing.

| Preset | What has to be built first |
| --- | --- |
| Machine knives | The profile import the PCD profile cutter design module already has, generalised. |
| Superabrasive wheels | A revolve body and a segment layout in the geometry kernel. |
| Woodworking cutter heads | An insert seat array on a revolve body. |
| Coating racks and jigs | A rack layout is a different modelling problem from a tool body. |

Solid carbide drills, reamers and countersinks share the solid carbide endmill's parameters and are not built yet.

### Ask for one

1. Open `/app/settings/presets` and choose the roadmap entry.
2. Choose **Request this build** and book a time to talk it through. Asking costs nothing.

### Something not on the list

1. At the foot of the list in `/app/settings/presets`, open **Nothing here matches what you sell?**
2. Under **A custom design module**, choose **Book a scoping call**, or **Write it down instead** to describe it in Support. Bring a drawing or the spreadsheet you price from today.

A custom design module is one-off work quoted per project, with no published range. Once live it runs on every plan, inside your plan's saved design and export allowances. See [Work quoted per project](/docs/billing/work-quoted-per-project).

# Docs: Route

## Route

URL: https://kabaido.ai/docs/route

Route takes the confirmed order and gets it to the customer's door.

Route takes the confirmed order and gets it to the customer's door.

It can plan the consignment, label the packages or load the van, hold the window you promised, track the courier, sequence a day of stops and capture the signature at the door from the driver's own screen. Field sales visits plan onto the same runs.

Give your customers a delivery date they can plan production around, and proof of what arrived and when.

It records every move as a scan event and books the real cost of the delivery against the job.

Run it with couriers, with your own vehicles, or both. With Kabaido Stock on, a van is a location and a load is a transfer.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

A consignment record for each delivery of an order, carrying the address, the promised window, the carrier or the internal run, the packages, the tracking reference and the proof of delivery. Runs carry a day of stops for one vehicle, loading says what goes on it, and the driver works from a station screen on a phone. Picking, packing, dispatch, delivery, failure and return each write a trace event in the same step as the state they set. What the carrier charged and each delivery's share of a run's cost are written against the delivery.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Route](/docs/areas/route) | `/app/route` | a full screen workbench |
| [Scan](/docs/areas/scan-station) | `/app/scan` | a station screen |

It adds to [Stock](/docs/areas/stock) when the product that brings that area is on too.

Works with [Stock](/docs/stock) and [Commerce](/docs/commerce). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Route workbench with deliveries, runs, vehicles and couriers, the Deliveries lens on Orders, and proof of delivery from the driver's own screen.

Switched off: Deliveries and runs stay readable. Nothing new can be planned or dispatched until it is switched on again.

### Who uses it

- Transport Manager
- Despatch Supervisor
- Warehouse and Goods Out team
- Drivers
- Field Sales
- Internal Sales answering "where is my order"

### Couriers, your own vans or both

| You ship by | What you use |
| --- | --- |
| Couriers only | [Deliveries](/docs/route/the-delivery-lifecycle) and [Couriers](/docs/route/couriers) at `/app/route`. |
| Your own vans | Deliveries, [Runs and Vehicles](/docs/route/vans-and-runs), [Loading](/docs/route/loading) and [the driver station](/docs/route/the-driver-station). |
| Both | All of it. Each delivery picks its means: carrier, own run or collection by the customer. |

Runs, Loading and Vehicles appear only when own transport is on for the workspace. It is off in a new workspace and there is no switch for it in Settings yet: ask through [Getting help](/docs/getting-started/getting-help).

## The delivery lifecycle

URL: https://kabaido.ai/docs/route/the-delivery-lifecycle

Raise a delivery from an order and move it from pending to delivered, knowing what each step does to the order and the stock.

Why: A customer planning production around your goods needs a date and a state they can trust.
What: A delivery is one consignment: goods from one order, to one address, in one window, by one means.
How: It moves through fixed states, and each move saves its trace event, its stock movement and the order's state in one step or not at all.

### Raise a delivery

1. Open `/app/route` (the **Deliveries** view) and choose **New delivery**.
2. Search the order by its number. Only orders with something outstanding to deliver are offered.
3. Pick the **Means**: **Carrier**, **Own run** or **Collection by customer**, then **Save**.
4. The draft carries every outstanding line at its outstanding quantity and the order's address. Open it to set the window and add packages.

An order may have several deliveries. With Route on, the Orders area gains a **Deliveries** view with every order's fulfilment state. **Create a delivery** on an order that has none raises one by carrier.

### The states

| State | Next moves in the drawer | What else happens |
| --- | --- | --- |
| Pending | **Mark ready** | Nothing prepared yet. |
| Ready | **Picked**, **Dispatch** |  |
| Picked | **Packed**, **Dispatch** |  |
| Packed | **Dispatch** |  |
| Dispatched | **Out for delivery**, **Delivered**, **Failed** | By carrier or collection, the goods are issued from stock. A confirmed order moves to in progress. |
| Out for delivery | **Delivered**, **Failed** |  |
| Delivered | **Returned** | On your own run with Stock on, the goods leave the van's stock now. When every line has arrived, the order is fulfilled. |
| Failed | **Rebook** | Needs a reason. The failed record stays. |
| Returned | None | The quantities reverse and the goods come back into stock. |

> A failed delivery is never edited into a success. **Rebook** creates a new pending delivery with the same lines and packages, and the failed one stays on the record.

**Delivered** needs a signature unless the workspace allows unsigned deliveries: see [Proof of delivery](/docs/route/proof-of-delivery).

### When stock did not hold it

Neither a dispatch nor a delivery from the van is refused for a balance. Each issues what the ledger holds and the drawer names every line that left the building without stock behind it, so the gap is seen rather than hidden.

### Documents

The drawer offers **Print delivery note**, **Print packing list** and **Print collection note**; none of them carries a price. **Print label** on each package prints its own label for scanning.

## Couriers

URL: https://kabaido.ai/docs/route/couriers

Record your carrier accounts, dispatch consignments against them and see what each one carried and cost this month.

Why: Whoever holds the carrier accounts needs the consignments, the tracking and the spend in one place.
What: The **Couriers** view at `/app/route?view=couriers` lists your carrier accounts with this month's consignments, packages, spend and on time rate.
How: You add each account once, then record the consignment reference and cost when you dispatch a delivery by carrier.

### Add a carrier account

1. Open `/app/route?view=couriers` and choose **Add carrier** (admin and above).
2. Pick the **Carrier** and fill **Account** and **Services offered** in your own words (next day, pallet, timed).
3. Set the **Default package** kind.
4. Paste the carrier's own **Tracking address** with `{reference}` where the consignment number goes, then **Save**.
5. In the list, type a consignment number into the **Tracking** column and choose **Test** to check the link.

> No tracking address ships prefilled. An invented tracking address is an invented fact, so the link renders only from the one you enter.

### Dispatch by carrier

On a delivery with the means **Carrier**, choose **Dispatch** and record the carrier, the **Consignment reference** and **What the carrier charged**. The carrier's own label comes from the carrier's system.

### What works with each carrier today

| What | Status |
| --- | --- |
| Royal Mail, Parcelforce, DPD, DHL Express, DHL eCommerce, UPS, FedEx, Evri, DX, APC Overnight, Palletways, Pall-Ex, The Pallet Network (TPN), Palletline and Fortec | **Template**: record the consignment by hand; the tracking link renders from your template. |
| Any other carrier | Add it as **Other carrier** and work the same way. |
| A connector that books, labels and tracks on its own | **Roadmap**, with no date. |

Without a connector, a consignment's state is whatever a person records on the delivery. The **Spend by carrier** card shows only what you entered, never an estimate, and **On time** counts only consignments with both a delivered time and a promised date.

## Vans and runs

URL: https://kabaido.ai/docs/route/vans-and-runs

Keep your vehicles, their capacity and their days off the road, and plan and close a day's run for each van.

Why: Your own vans cost money per kilometre and per hour, and a day of stops only works in a sensible order.
What: **Vehicles** at `/app/route/vehicles` holds the vans; **Runs** at `/app/route/runs` holds a day of stops for one vehicle.
How: The planner orders the stops by their windows and straight line distance, and closing the run records the odometer and shares the cost across what it carried.

> Runs, Loading and Vehicles appear only when own transport is on for the workspace. It is off in a new workspace and there is no switch for it in Settings yet: ask through [Getting help](/docs/getting-started/getting-help).

### Vehicles

**Add vehicle** records the registration, name, kind, capacity in kilograms and cubic metres, **Cost per kilometre**, **Cost per hour**, **MOT due** and **Service due**. Under **Off the road**, **Add a date range** with a reason; on those days the list shows **Off the road on this date**. An MOT or service coming up is flagged **Due within thirty days**.

### Plan a run

1. Open `/app/route/runs` and pick the run from the week strip.
2. Choose **Add stop** for a site you are planning by hand. A new stop goes last.
3. Choose **Sequence**: stops with a window go first in window order, then the nearest next, from the depot. Dragging a stop or **Lock the order** keeps your own order; **Unlock the order** to sequence again.
4. A stop with no coordinates sorts last and asks you to **Pin this address** on the map. Nothing is guessed from the address.
5. **Open in Google Maps** hands the pinned stops to the satnav; **Open in Waze** goes to the next pending stop, as Waze takes one destination at a time. **Print manifest** prints the stops in order with their packages.

Distances are **planned, straight line**. Actual kilometres come from the odometer when the run closes.

### Close a run

**Close run** asks for the odometer reading and the minutes on the road, and is refused while a stop is still pending: defer each one with a reason first. It warns of packages still on the van, to rebook as failed or adjust with a reason. The cost is shared across the deliveries by packages, weight, stops or value, and stays a planned cost when no reading was taken before the van left.

> Starting a new run, giving it its van and driver, putting a delivery on a stop and binding a driver station to a van are not on these screens yet. Ask through [Getting help](/docs/getting-started/getting-help).

## Loading

URL: https://kabaido.ai/docs/route/loading

Scan every package onto the van in reverse stop order and leave only when the load is complete or the shortfall is explained.

Why: A package left on the dock is a failed stop before the van has left.
What: **Loading** at `/app/route/loading` shows one run's packages grouped by stop, with expected, loaded and missing counts.
How: Each scan ticks a package aboard and writes its trace event; **Depart** asks for a reason if anything is missing.

> Runs, Loading and Vehicles appear only when own transport is on for the workspace. It is off in a new workspace and there is no switch for it in Settings yet: ask through [Getting help](/docs/getting-started/getting-help).

### Load a van

1. Open `/app/route/loading`. It opens today's run; pick another of today's runs if there is more than one.
2. Scan each package label into **Scan a package** with a wedge scanner or **Use the camera**, or type the code in. The list runs **Last stop first** so the first drop comes off first; switch to **First stop first** if you load the other way.
3. Scanning a package that is already aboard takes it off the van again.
4. Add a customer's own goods riding on the van with **Add a parcel that is not ours**, so the manifest is complete.
5. Enter the **Odometer before leaving** if you want actual kilometres at the close, then choose **Depart**.

**Load all remaining** marks the rest loaded without scanning, after a confirmation. The **Carried** bar shows weight and volume against the van's **Capacity** and warns without blocking.

### With Stock and without

|  | What a load does |
| --- | --- |
| With [Stock](/docs/stock) on | The van is a stock location and each scan is a transfer onto it, visible in the ledger. |
| Without Stock | The package is ticked against its stop and nothing moves between locations. |

A driver can also load from the phone: **Load the van** on the [driver station](/docs/route/the-driver-station) scans into the same run.

## The driver station

URL: https://kabaido.ai/docs/route/the-driver-station

Drive a day's run from a phone: the next stop, navigation and the outcome at each door, with or without signal.

Why: A driver at a door needs one thing at a time, and the record of it must not depend on signal.
What: The driver station at `/app/route/drive` shows today's run for the van, the **Next stop** as a large card and the stops below it.
How: Every action is saved on the phone first and sent when the network is there, stamped with the time it happened.

### Two ways in

| Who | How |
| --- | --- |
| A van's phone | A station in the Route area, created in [Settings then Organisation](/docs/areas/settings#organisation) under **Stations**, signs in at `/station` with its device key and lands here. It shows the run of the van it is bound to. Binding a station to a van is not on the screens yet: ask through [Getting help](/docs/getting-started/getting-help). |
| A colleague who drives | A member given the **Driver** template opens the van from **Stations** in their own menu, under their own sign in, and sees the run they are named driver on. |

### At each stop

1. Read the card: customer, address, window, what is **On this stop** and the **Instructions**. **Google Maps**, **Waze** and **Call** are one tap.
2. Choose **Delivered**: ask them to sign, enter the **Printed name** and **Add a photograph** if useful.
3. Or **Collected** for goods coming back, or **Failed** with a **Reason** (closed, refused, no access, damaged, wrong address, not ready, vehicle, other) and a note.
4. When every stop is done, choose **Close the run** and enter the odometer and the minutes on the road.

### Offline

The bar shows **Offline** and how many actions are waiting to send; nothing blocks. Photographs wait on the phone up to 25 MB, above which the driver is asked to get back on the network before taking more.

> A driver never sees a price, a cost rate or a customer's terms: those columns are not sent to the station at all.

## Proof of delivery

URL: https://kabaido.ai/docs/route/proof-of-delivery

Know what proof a delivery carries, where it is recorded and what your customer sees of it.

Why: "Where is my order" and "we never received it" are answered by proof, not by a status.
What: Proof is the signature, the printed name, any photographs and the trail around them: the time, the place, the device and who was signed in.
How: It is written on the delivery's trace event in the same step as the delivered state, so the state never exists without it.

### What is recorded

| Field | Where it comes from |
| --- | --- |
| **Signature** | Drawn on the driver station. |
| **Received by** | The printed name, required for a signed delivery. |
| **Photographs** | Taken on the driver station. |
| **Delivered** | The time of the action on the phone, not the time it was sent. |
| **Place** | The phone's location, where the driver allowed it. |
| **Device** | The device the action was recorded on. |

The office drawer's **Delivered** asks for who took it and how much arrived, with no signature. Only a workspace that allows unsigned deliveries can record one there. That is off by default with no switch in Settings yet, so ask through [Getting help](/docs/getting-started/getting-help); until then a delivery is signed on the driver station.

> A drawn signature is an electronic signature. What stands behind it is the trail, and Kabaido claims no more legal weight for it than that.

### Where you see it

- In the delivery drawer at `/app/route`, under **Proof of delivery**.
- With [Commerce](/docs/commerce) on, your signed in customer sees the signature, the name and the time on their own delivery. Photographs are not shown to them.

# Docs: Source

## Source

URL: https://kabaido.ai/docs/source

Source runs your buy side, from the request for quotation to the invoice matched against what arrived.

Source runs your buy side, from the request for quotation to the invoice matched against what arrived.

It can hold your suppliers and their price lists, send a request to many of them at once, bring the answers back comparable, raise the purchase order, chase the acknowledgement and book the goods in, all beside your sales orders rather than in a separate system.

Give your customers a price built on what you actually pay today and a date you can commit to, because the buying and the selling share one set of numbers.

With Kabaido Stock on, receipts land in the ledger, on order quantities are visible and reorder points become actions.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

A supplier master beside the customer master, price lists whose best price you can accept as cost, outbound requests for quotation at scale with comparable answers, purchase orders under the Purchase view of the same Orders area as sales orders, goods receipts and invoice matching. Supplier replies that carry the request number are filed by the same email agent that reads customer mail.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Suppliers](/docs/areas/suppliers) | `/app/suppliers` | an area in the menu |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | an area in the menu |

It adds to [Stock](/docs/areas/stock) when the product that brings that area is on too.

Works with [Stock](/docs/stock). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings Suppliers, supplier quotes, purchase orders under Orders and suppliers' prices in the Catalogue.

Switched off: Suppliers, price lists and purchase orders stay readable. Nothing new can be requested or raised until it is switched on again.

### Who uses it

- Purchasing Manager
- Buyer
- Procurement Coordinator
- Stores and Goods In
- Accounts Payable

### The buy side, step by step

| Step | Where | Read |
| --- | --- | --- |
| Hold your suppliers | `/app/suppliers` | [Suppliers](/docs/source/suppliers) |
| Load what they charge | `/app/suppliers?view=price-lists` | [Price lists](/docs/source/price-lists) |
| Ask many at once | `/app/suppliers?view=rfqs` | [Requests for quotation at scale](/docs/source/requests-for-quotation-at-scale) |
| Order | `/app/orders?view=purchase` | [Purchase orders](/docs/source/purchase-orders) |
| Receive | The order, or `/app/scan` where the [Scan station](/docs/areas/scan-station) is in the workspace | [Goods in](/docs/source/goods-in) |
| Compare and cost | `/app/catalog?tab=suppliers-prices` | [Price analysis](/docs/source/price-analysis) |

## Suppliers

URL: https://kabaido.ai/docs/source/suppliers

Add suppliers, keep their contacts and terms in one record and see how each one performs.

Why: Buying well starts with knowing who you buy from, on what terms and how reliably.
What: The Suppliers area holds one record per supplier, beside your customers, with contacts, terms, prices, quotes, orders and performance.
How: Open `/app/suppliers`, add or import suppliers, then work from each record.

### Add suppliers

1. Open `/app/suppliers` on the **Suppliers** view.
2. Choose **New supplier** and give the company, currency, payment terms, lead time and the categories it supplies.
3. Or choose **Import suppliers** with a CSV that has a `company` column; `email_domain`, `vat_number`, `currency`, `payment_terms`, `lead_time_days`, `categories` and `account_ref` are optional.
4. Or choose **From a customer** for a company you both buy from and sell to. It copies the company, its addresses, VAT number and contacts and links the two records.

### The supplier record

| Tab | What it holds |
| --- | --- |
| Overview | Trading terms (status, currency, payment terms, incoterm, lead time, minimum order value, carriage paid over, freight, duty), categories, website, email domain, VAT number, rating, notes and approval |
| Contacts | Their people and the one primary contact a request goes to by default |
| Prices | Their price lists |
| Quotes | Every request sent to them and its state |
| Orders | Their purchase orders |
| Performance | Orders and lines in twelve months, on time, average days late, received, rejected, purchase price variance, spend and last order |

**Prices**, **Quotes** and **Orders** show only to a role that can see cost. From the record: **Request a quote**, **Raise a purchase order**, **Add a price list** and **Archive**. An archived supplier takes no new requests or orders; its history stays.

> The Performance tab states how many lines its figures rest on. Under five lines the count is shown and no percentage, so one late delivery never reads as a trend.

### Contacts in one list

The **Contacts** view lists every supplier contact with the requests sent and when they were last contacted, so a bounced address is fixed without opening each record.

### Who can do what

- Sales and above add, edit and archive suppliers and contacts.
- Engineer and above request quotes, raise purchase orders and import price lists.
- Only an admin approves a supplier or withdraws the approval.
- Freight and duty terms feed the landed cost on [Price analysis](/docs/source/price-analysis).


## Price lists

URL: https://kabaido.ai/docs/source/price-lists

Import a supplier's price list, match it to your catalogue and make it the price on offer.

Why: A price you pay only counts once it sits against the product you sell.
What: A price list is one supplier's prices in one currency, with breaks, validity and a match to your catalogue for every row.
How: Import the supplier's CSV, clear the unmatched rows, then activate the list.

### Import a list

1. Open `/app/suppliers?view=price-lists` and choose **Import CSV**, or **Add a price list** on the supplier's record.
2. Pick the supplier, name the list, set its currency and its valid from and valid to dates, then choose the file.
3. The columns are `supplier_sku`, `description`, `sku` (yours), `min_qty`, `unit_price`, `currency`, `uom`, `pack_qty`, `moq`, `lead_time_days`, `valid_from` and `valid_to`.
4. Each row is matched by your SKU, or by the supplier SKU already linked to a product. The message says how many rows came in and how many matched.

### Match and activate

1. Open the list. The **Unmatched** tab holds every row with no product: type your SKU under **Search your catalogue** and choose **Match**. The supplier's SKU stays linked to that product for the next import.
2. The **Changes** tab compares the list with the newest superseded list for the same supplier and currency: new rows, removed rows and price moves.
3. Choose **Activate**. The previous active list for the same supplier and currency is superseded in the same step.

| Status | Meaning |
| --- | --- |
| Draft | Imported, not yet on offer. Only a draft can be deleted, with **Delete draft** |
| Active | The supplier's current prices; the best active price per product shows on [Price analysis](/docs/source/price-analysis) |
| Superseded | Replaced by a newer list or retired with **Supersede**, kept for the history |

> Activating a list does not change your cost. Accepting a supplier price as cost is a separate decision, made on [Price analysis](/docs/source/price-analysis), unless an admin has switched automatic acceptance on.

When activating leaves a product's best price beyond the price change alert from its current cost, the workspace gets a notification. The alert percentage sits in the Source block of [Settings then Organisation](/docs/areas/settings#organisation).


## Requests for quotation at scale

URL: https://kabaido.ai/docs/source/requests-for-quotation-at-scale

Send one request to many suppliers, compare the answers line by line and award the winners.

Why: Asking five suppliers the same question should take the time of asking one.
What: A request is one set of lines sent to many suppliers, each with their own answer link and their own supplier quote.
How: Build the lines, pick the suppliers, send, then compare and award from the request.

### Build and send

1. Open `/app/suppliers?view=rfqs` and choose **New request**. **Request a quote** on a supplier's record starts one for you, as do **Build a shortage list** and **Request quotes** on the Stock **Reorder** view.
2. On **Lines**, search the catalogue or choose **Add a line** for something you do not stock. Set the quantity, unit, need by date and target price.
3. On **Suppliers**, tick who to ask. Suppliers already linked to the saved lines are listed first, so choose **Save** after adding lines by hand. Choose a contact (the primary contact is picked for you) and a channel: **Email**, or **Link only** when you send the answer link yourself.
4. On **Settings**, set **Currency requested**, **Due**, **Deliver to**, **Incoterm** and whether suppliers may quote their own break quantities.
5. Choose **Send request**. Each supplier gets their own answer link and sees only their own prices.

A request carries at most 200 suppliers, and a workspace sends at most 2,000 request emails a day.

### How answers arrive

| Channel | What happens |
| --- | --- |
| Answer link | The supplier opens `/q/<token>`, types prices, lead time and validity, then chooses **Save draft**, **Submit** or **Decline** |
| Email reply | With an inbox connected to the email agent, a reply carrying the request number is filed against the supplier quote with that number and the person who raised the request is told; you type the prices with **Enter answer** |
| By hand | **Enter answer** on the **Recipients** tab, beside a supplier who has not answered. A price you do not have stays blank, never zero |

### Compare and award

1. Open the **Comparison** tab: a row per line, a column per supplier that answered. Switch the basis between **Quoted price**, **Landed cost** and **Lead time**.
2. Choose **Award best price** or **Award best landed cost**, or pick a cell per line by hand, then **Award**.
3. One draft purchase order is raised per winning supplier. Nothing is sent to anybody until you send the orders.

Every supplier quote also appears in `/app/quotes?view=supplier`. A supplier quote is cost, never a sell price; it never counts in the sales pipeline.


## Purchase orders

URL: https://kabaido.ai/docs/source/purchase-orders

Raise, send, track and close a purchase order, and match the supplier's invoice to what arrived.

Why: What you have on order decides what you can promise a customer.
What: A purchase order is an order in the Orders area under the **Purchase** view, beside your sales orders.
How: Raise it, send it to the supplier, receive against it and record their invoice.

### Raise and send

1. Open `/app/orders?view=purchase` and choose **New purchase order**. An award, **Raise a purchase order** on a supplier's record and **Raise a purchase order** on the Stock **Reorder** view open one for you.
2. Pick the supplier and contact, the expected date and **Ship to**, then add lines from the catalogue or by hand, with their unit prices.
3. Choose **Save**, then **Send to supplier**. The PDF is stored, the email goes to the contact and on order quantities rise.
4. When the supplier confirms, choose **Mark acknowledged**.

> Sending needs an admin unless the Source block in [Settings then Organisation](/docs/areas/settings#organisation) lets engineers send. A price changed after sending asks for a reason, which goes on the trail.

### States

| State | What it means | What you can do |
| --- | --- | --- |
| Draft | Nothing has left the building | Edit, send, cancel |
| Sent | With the supplier | Acknowledge, receive, edit, cancel |
| Acknowledged | The supplier has confirmed | Receive, edit, cancel |
| Part received | Some lines are still outstanding | Receive, close |
| Received | Every line is in | Close |
| Closed | No further receipt is accepted | Nothing |
| Cancelled | Withdrawn before anything arrived | Nothing |

**Overdue** is a flag, not a state: sent, past its expected date and still outstanding. The Purchase view filters on it. Once anything is received the order can no longer be cancelled: close it instead.

### The supplier's invoice

An admin records the invoice reference, amount and dates on the **Supplier invoice** block with **Record invoice**. Kabaido matches it against what was ordered and what arrived.

| Result | Meaning |
| --- | --- |
| Matched | The amount equals the value received, within your tolerance |
| Price variance | The amount differs from the value received by more than your tolerance |
| Quantity variance | The invoice bills more than arrived (only an invoice sent through an [inbound endpoint](/docs/api/inbound-endpoints) carries a quantity) |
| Over billed | The invoice exceeds the order total |
| Unmatched | No invoice yet, or nothing received |

A matched invoice on a fully received order closes the order. An admin can **Acknowledge variance** once a variance is understood. Kabaido records the match; it posts nothing to your accounting system.

## Goods in

URL: https://kabaido.ai/docs/source/goods-in

Book a delivery in against its purchase order, at the desk or at the scan station.

Why: Stock, cost and the order's state should change the moment a delivery is counted.
What: A receipt books what arrived against a purchase order and posts it to stock in one step.
How: Choose **Receive** on the order, or find the order number at `/app/scan`, then post the receipt.

### From the order

1. Open the purchase order and choose **Receive**. Every outstanding line is listed, defaulted to what is outstanding.
2. Enter what arrived under **Received** and the **Delivery note reference**. Enter anything refused under **Rejected** with a **Reject reason**. With more than one location, pick the **Stock location**.
3. Choose **Post receipt**.

### At the scan station

With Source on, the [Scan station](/docs/areas/scan-station) at `/app/scan` carries a **Receive** panel (the Scan station comes with Stock, Route, Service Centre or Machinist, not with Source alone): type or scan the **Purchase order number**, choose **Find**, enter the quantities and choose **Post receipt**. The station shows quantities only: no unit price, line total or order value.

### What posting does

- Checks each line against what is outstanding. Receiving more than is outstanding is refused unless **Over receipt allowed, per cent** in the Source settings gives a margin.
- Mints a lot code per received line, so the batch can be traced.
- Writes a receipt movement through the one stock writer, carrying the landed unit cost.
- Updates the received quantity, the order's state and the on order figure.

Either all of it happens or none of it does.

### Where it lands

At the location picked on the receipt, otherwise the order's **Ship to**, otherwise the organisation's default location. The movement is written whether Stock is on or off, so a workspace that switches Stock on later finds its goods in history already on the ledger. See [Movements and the ledger](/docs/stock/movements-and-the-ledger).

> A posted receipt cannot be reversed from the order. Correct a miscount with **Adjust** on the stock line in [Stock](/docs/stock/items-and-balances), which asks for a reason and needs the Stock product on.

## Price analysis

URL: https://kabaido.ai/docs/source/price-analysis

See who is cheapest for each product, what it really costs landed and accept a supplier price as your cost.

Why: A margin is only honest when the cost under it is what you pay today.
What: Source compares supplier prices per product, works out landed cost and offers the best price as your cost.
How: Use the **Suppliers' prices** view in the Catalogue, the request comparison and each supplier's Performance tab.

### Suppliers' prices

Open `/app/catalog?tab=suppliers-prices`. It needs Source on and a role that can see cost.

| Mode | What it shows |
| --- | --- |
| **By product** | The default supplier, the best active price and who gives it, suppliers quoting, lead time, your current cost and how far the best price sits from it |
| **By supplier** | Rows quoting, products covered, the active list, the last import and how many products they are cheapest on |

### Accept a price as cost

1. In **By product**, tick the products whose cost should follow the supplier.
2. Choose **Accept as cost**. The best active price for one unit, in your currency, becomes the product's cost and the row is marked **Cost basis**. A price with no accepted exchange rate is skipped.
3. Where a product has no default supplier, **Set default supplier** makes the supplier with the best price its default.

> Nothing becomes cost on its own. Kabaido shows the drift; you decide. An admin can switch on **Accept a price list as cost when it is activated** in the Source settings, which accepts the prices that moved beyond the alert.

### Landed cost

Landed cost adds the supplier's freight and duty to the goods and converts into your currency. The request comparison uses it for **Landed cost** and **Award best landed cost**.

| Freight | How it is added |
| --- | --- |
| None | Nothing |
| Per order | Shared across the lines on the order |
| Per line | Added to each line |
| Per cent of value | A share of the goods value |
| Per kg | Needs the product's weight; where none is known, no landed figure is shown rather than a guess |

Duty is a percentage of goods plus freight. A currency converts only at a rate an admin has added under **Accepted exchange rates** in the Source settings; without one a price shows **No rate set** rather than a guess.

### Performance over time

Each supplier's **Performance** tab shows twelve months of purchase price variance (landed cost against the ordered price), spend, on time delivery and rejections, with the number of lines they rest on. See [Suppliers](/docs/source/suppliers).

# Docs: Stock

## Stock

URL: https://kabaido.ai/docs/stock

Stock keeps one true quantity for everything you hold, wherever it is.

Stock keeps one true quantity for everything you hold, wherever it is.

It can run your locations, transfers, stocktakes and reorder points, and records every movement as it happens: goods received on a purchase order, material consumed at a machine, a load leaving on a van.

Give your customers an availability answer you trust at the moment of quoting, and fewer promises you have to take back.

Every balance is derived from the ledger rather than typed over, so each change carries a reason, a person and a time.

It works with the rest of the platform, or on its own for a stores operation or a distributor that needs inventory and nothing else.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Stock runs locations, lines, an append only movement ledger and counts, with a single writer that every other product calls. Balances are derived from the ledger and never edited. It adds a location tree with scannable codes, transfers between locations, stocktakes that write their own variance adjustments, and reorder points watched by the Reorder view and the stock monitors.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | an area in the menu |
| [Stock](/docs/areas/stock) | `/app/stock` | an area in the menu |
| [Scan](/docs/areas/scan-station) | `/app/scan` | a station screen |

It adds to [Quotes](/docs/areas/quotes) and [Orders](/docs/areas/orders) when the product that brings those areas is on too.

Works with [Design Engineer](/docs/design-engineer), [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Machinist](/docs/machinist). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Stock area with lines, locations, movements and reorder points, plus the Products, Schemas and Imports views of the Catalogue.

Switched off: Every balance stays correct and every movement stays recorded. Locations, counts and reorder points are not available until it is switched on again.

### Who uses it

- Stores Manager
- Inventory Controller
- Goods In and Goods Out
- Production Planner
- Internal Sales checking availability

### What a workspace without Stock still gets

The ledger is infrastructure, not the product. Every workspace has one default store, and every quantity any product changes is written as a movement whether Stock is on or not.

- The catalogue's stock figure and the products API read the same true balance.
- Each product keeps its own quantity surface: the design module's stock lines, the machine module's stock, goods in against a purchase order and the issue on delivery.
- Switching Stock on later reveals the history that was recorded all along. Switching it off loses nothing: the area stays readable, without its write controls, until it has no rows.

What needs the product: more [locations](/docs/stock/locations), transfers, [counts](/docs/stock/counts-and-stocktakes), [reorder points and the stock monitors](/docs/stock/reorder-points-and-monitors), the [ledger screen](/docs/stock/movements-and-the-ledger), the [stock moves on the Scan station](/docs/stock/scanning-stock) and the stock questions in the AI.

## Items and balances

URL: https://kabaido.ai/docs/stock/items-and-balances

Read a balance by item and location, and change it the right way when it is wrong.

Why: A quantity someone types over cannot be trusted, so nobody types over one here.
What: A line is one item at one location, and its balance is the sum of its movements.
How: Open `/app/stock`, find the line in the **Lines** view and record a movement from its drawer.

### The Lines view

| Column | Means |
| --- | --- |
| **On hand** | What the ledger says is at this location. |
| **Reserved** | Held for open orders. |
| **Free** | On hand less reserved. |
| **On order** | Due in on open purchase orders. |
| **Reorder point** | The level the Reorder view watches. |
| **Unit cost** | The moving average, recomputed on every receipt. Engineer and above only. |

Filter by location, kind (**Product**, **Design**, **Material**, **Consumable**, **Part**), source, or **Under reorder point**. **Export** takes the filtered rows.

### Where lines come from

- A catalogue product imported or saved with a quantity opens a line with an **Opening** movement.
- Goods in, a design module and a machine module open lines as they first move stock.
- **Add a line** is for something the catalogue does not carry, such as a consumable. It starts at zero.

### Change a balance

1. In `/app/stock`, choose the line to open its drawer.
2. Choose **Adjust**, **Transfer**, **Write off**, **Return** or **Receive by hand**. The actions show to engineer and above.
3. Enter the quantity and a **Reason** (a transfer asks for **Transfer to** instead), then choose **Record**.

> A movement that would take a balance below zero is refused, never quietly clamped. Only a location set to **May go below zero** accepts one.


## Locations

URL: https://kabaido.ai/docs/stock/locations

Set up the stores, bins and other places stock is held, and give each a scannable code.

Why: A balance is only useful if it says where the stock is.
What: Locations form a tree: a store, the bins inside it, and the vans, stations and customers that hold stock too.
How: Open `/app/stock`, choose **Locations** and use **Add a location**.

### Add a location

1. In `/app/stock`, choose the **Locations** view, then **Add a location**.
2. Give it a **Name** and a **Kind**, and choose where it sits under **Inside** (or **Top level**).
3. Add a **Scannable code** if the shelf will carry a label, then **Save**.

### Kinds

| Kind | Offered when |
| --- | --- |
| **Store**, **Bin**, **In transit** | Always. |
| **Vehicle** | Route is on. |
| **Station** | Machinist is on. |
| **Customer** | Service Centre is on. |

Every workspace starts with one store, marked **Default**. Anything recorded without a location lands there.

### Rename, archive and go below zero

- **Rename** changes the name, code, parent and the below zero setting.
- **Archive** stops new stock arriving and keeps the history in the ledger. Only an empty location can be archived, and never the default store.
- **May go below zero** suits a van between its load scan and its reconciliation. Every other location refuses a negative balance.

Creating, renaming and archiving a location needs the engineer role or above.

## Movements and the ledger

URL: https://kabaido.ai/docs/stock/movements-and-the-ledger

Trace any balance back to the movements that made it, and export them.

Why: Finance and the stores both need to know why a number is what it is.
What: The ledger is append only: every change is a movement with a reason, a person and a time, and nothing edits one afterwards.
How: Open `/app/stock` and choose **Movements**, newest first.

### Movement kinds

| Kind | Written when |
| --- | --- |
| **Opening** | A quantity is first recorded, by import or by a product's own screen. |
| **Receipt** | Goods in posts against a purchase order, or someone uses **Receive by hand**. |
| **Reservation**, **Release** | An order is created or reopened, or is cancelled. Only the reserved figure moves. |
| **Issue** | An order is fulfilled, a delivery is dispatched by carrier or collection, or a van delivers it. |
| **Consumption** | A machine run uses material. |
| **Transfer** | Stock moves between locations, including onto a van. |
| **Adjustment** | A count variance, a correction with a reason, or a changed figure on a product's own screen. |
| **Return** | A delivery comes back, or someone records a **Return** by hand. |
| **Write off** | Stock is scrapped, with a reason. |

### Find and export

Filter by kind, location, who recorded it (**Member**, **Station**, **System**, **Integration**, **AI**, **Customer**) and date. **Export** takes the filtered rows as a file. Unit cost shows to engineer and above.

> Without the Stock product the movements are still written, and each product shows its own quantities. Switching Stock on opens the whole ledger here.


## Counts and stocktakes

URL: https://kabaido.ai/docs/stock/counts-and-stocktakes

Count a location and let the platform write the differences as adjustments.

Why: Shelves drift from the books, and a count is how you bring them back.
What: A count lists every line at one location with what the ledger expects; closing it writes one adjustment per difference.
How: Open a count from the **Locations** view of `/app/stock`, enter what you find and close it.

### Run a count

1. In `/app/stock`, choose **Locations**, then **Count this location** on the row.
2. Enter the figure found against each item in **Counted**. **Variance** fills in as you go.
3. Choose **Close the count** and confirm.

Closing writes every non zero variance as an **Adjustment**, in one transaction, and tells the team in Activity. A line left blank is not adjusted.

### Who does what

| Step | Role |
| --- | --- |
| Open and close a count | Engineer and above |
| Enter counted figures | Operator and above |

**Recent counts**, under the locations, shows each count's status, how many lines are counted and how many carry a variance.

> For one item on one shelf, the **Count** action on the Scan station is quicker. See [Scanning stock](/docs/stock/scanning-stock).

## Reorder points and monitors

URL: https://kabaido.ai/docs/stock/reorder-points-and-monitors

Set a reorder point on a line and have the team told when stock runs low.

Why: Running out is found too late when someone has to notice it.
What: A line at or under its reorder point shows on the Reorder view, and the stock monitors watch for low stock on a schedule.
How: Set the point in the line's drawer, then add a monitor from **Monitors** in `/app/stock`.

### Set a reorder point

1. In `/app/stock`, open the line.
2. Enter the **Reorder point** and, if you like, the **Reorder quantity**.
3. Choose **Save reorder point**.

### The Reorder view

**Reorder** lists every line at or under its point, with a **Suggested** quantity: the reorder quantity (or the gap to the point) less what is on order. **Export** takes the list.

With Source on, **Build a shortage list** takes every row to a request for quotes. Tick rows and it becomes **Request quotes**, beside **Raise a purchase order**. See [requests for quotation at scale](/docs/source/requests-for-quotation-at-scale) and [purchase orders](/docs/source/purchase-orders).

### The stock monitors

| Monitor | Fires when | Checked |
| --- | --- | --- |
| **Stock below a level** | A line of the chosen product falls under the level you set, at one location or at any. | Hourly |
| **Reorder point reached** | A line of the chosen product has on hand plus on order at or under its reorder point. | Daily |

Choose **Monitors** at the top of `/app/stock`, pick one under **Add a monitor**, fill it in and choose **Add it**. A fired monitor tells the team in Activity, once a day per line. Creating one needs the engineer role or above.

> The stock monitors need the Stock product. Switch it off and they pause rather than delete.


## Scanning stock

URL: https://kabaido.ai/docs/stock/scanning-stock

Move and count stock at the shelf with a scanner, without a keyboard.

Why: A stores person has a scanner in one hand and stock in the other.
What: The Scan station's **Stock** panel takes a location code, then an item code, and records a move or a count.
How: Open `/app/scan`, scan the shelf, scan the item and choose **Record**.

### Move or count

1. At `/app/scan`, scan the shelf into **Location code**. It stays held for the next item.
2. Scan the item into **Item code or SKU** and set the **Quantity**.
3. Choose **Move here** or **Count**, then **Record**.

| Action | Writes |
| --- | --- |
| **Move here** | A **Transfer** into the scanned location from wherever the item is now. |
| **Count** | An **Adjustment** that sets the balance here to what you found. |

The item code can be a SKU or a lot code, such as one minted at goods in. The location code is the **Scannable code** set on the location.

### Who can scan

- A member of operator rank or above, signed in as themselves.
- A station signed in with its device key. A station bound to a location may move stock only there.

> The Stock panel appears only with the Stock product on; the trace scans on the same screen work without it. Stock moves need a connection and are not queued offline.

# Docs: Service Centre

## Service Centre

URL: https://kabaido.ai/docs/service-centre

Service Centre runs the work you do on the customer's own property, from the item arriving to the item going back.

Service Centre runs the work you do on the customer's own property, from the item arriving to the item going back.

It can register the item with a scannable code, move it through the benches your workflow declares, price the job on what was found rather than what was declared, and turn the minutes between scans into real cost and visible margin.

Give your customers a clear account of where their items are, what was done and why it cost what it cost.

Its rules decide what is asked, surcharged, refused or defaulted before anyone types anything, so the quote is right the first time.

Built for reconditioning, coating, calibration and repair.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Service models declare a workflow type, the item families they apply to, their steps against station groups, a price formula and standard minutes. Registration gives the customer's item a code that prints as a QR and a Code 128 line on its docket and labels. Every scan lands on one trail, and the minutes between scans show on the item. The Costing view holds your rates and standard minutes and runs the reports, the Rules view records the workshop's settings, and with Commerce on, customers see their own items. Service models come ready for common work or are built to order.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Servicing](/docs/areas/servicing) | `/app/servicing` | an area in the menu |
| [Scan](/docs/areas/scan-station) | `/app/scan` | a station screen |

It adds to [Stock](/docs/areas/stock) when the product that brings that area is on too.

Works with [Stock](/docs/stock) and [Commerce](/docs/commerce). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings Servicing with the registry, the work queue, your services and their rules, and service lines on quotes and orders.

Switched off: Every registered item and its history stay readable. No item can be booked in or moved until it is switched on again.

### Who uses it

- Service Manager
- Workshop Supervisor
- Bench Operators and Grinders
- Goods In
- Internal Sales quoting service work
- Quality Manager

### Where to start

1. In `/app/settings/presets`, open the preset for your trade in the **Service centres** group and choose **Turn on** ([which ones](/docs/service-centre/custom-and-paid-setup)).
2. Open `/app/servicing?view=services`, put your own rates into each service and choose **Switch this service on** from its row's menu.
3. Choose **Register item** on the Work view and book the first item in. [The registry and the item lifecycle](/docs/service-centre/the-registry-and-item-lifecycle) takes it from there.

## Service models and workflow types

URL: https://kabaido.ai/docs/service-centre/service-models-and-workflow-types

Set up a service that prices itself, and know which workflow type your work follows.

Why: A service priced by hand is priced a little differently by every person who quotes it.
What: A service model is the setup behind one kind of work: its workflow type, families, steps, price formula and standard minutes.
How: Install one from a preset or start a service in `/app/servicing?view=services`, then tune it in the builder.

Screenshot of /app/servicing?view=services: The Servicing area on its Services view: the services the tool regrind preset installed, each waiting for your own rates before it switches on.

### The workflow types

The type decides the default steps a preset writes into the model's workflow.

| Type | The work |
| --- | --- |
| **Product servicing** | The customer's own item comes in, is worked on and goes back. |
| **Batch process** | A quantity arrives as one lot, is processed together and is counted out. |
| **Site visit** | The work happens at the customer's site. |
| **Bench work** | Work on something already in the building, with no collection or return. |

The type, the families and the steps arrive with a service centre preset and are not edited in the workspace. The builder edits the price, the item defaults and the tests.

### Start a service

1. Open `/app/servicing?view=services` and choose **From a template** or **Blank**.
2. A template arrives paused with illustrative rates and reads **Set your rates to switch it on** until you have.
3. Open the service to tune it in the builder at `/app/servicing/services/[id]`. Back in the list, choose **Switch this service on** from its row's menu.

### The builder

| Section | What you set |
| --- | --- |
| **Service details** | Name, domain, description and **Subject to inspection**. |
| **Item lifetime and limits** | **Default max services**, **Turnaround** in working days and serviceability **Limits**. |
| **Parameters** | What the customer or inspector fills in: number, dimension, select, boolean or text. |
| **Pricing** | Derived values, then outputs. `price`, `cost` and `leadtime_days` are the standard keys. |
| **Rules** | **Block** stops the run with its message; **Warn** attaches it and carries on. |
| **Test bench** | Try inputs, **Check on server** and **Save current** as a test. |

The Endmill regrind and recoat template prices like this, at its illustrative rates:

```text
base = tiered(diameter_mm, [[0,8.50],[6,10.00],[12,14.00],[20,22.00]])
price = round((base + flutes * 0.85) * lookup_meta('regrind_faces','f') + if(coating_strip, 4.50, 0), 2)
leadtime_days = if(coating_strip, 7, 4)
```

> Saving runs every saved test. A service stays on only while it has a price output and every saved test is green; otherwise it pauses itself and says why, and **Switch back on** returns it once the tests pass.

### Services per plan

| Free | Pro | Ultra | Max |
| --- | --- | --- | --- |
| 2 | 25 | Unlimited | Unlimited |

Interactive example: A preset service model's stations in order, with one item going through them.

## Families

URL: https://kabaido.ai/docs/service-centre/families

Know what an item family is, which ones the presets bring and what a family changes today.

Why: A saw blade and a knife set are measured differently, so one form for both asks the wrong questions.
What: A family is a class of item with its own fields: what the item is, entered once, and what is measured at every service.
How: A service centre preset installs the families for its trade, each with its three sets of fields.

### Three sets of fields

| Set | Filled in | Example |
| --- | --- | --- |
| **Stock fields** | Once, when the item is first described. | Diameter, bore, teeth. |
| **Condition fields** | At every inspection. | Teeth to replace, run out. |
| **Final check fields** | A short subset, checked before the item goes back. | Diameter after grind. |

### The families the presets bring

| Family | Measured each service |
| --- | --- |
| **Circular saw blades** | teeth broken, teeth to replace, diameter after grind, kerf after grind, run out, cracks and resharpen area left |
| **Bore cutters and hoggers** | teeth broken, teeth to replace, width after grind and run out |
| **Shank tools** | diameter after grind, length after grind, chipped edges and run out |
| **Planer and profile knives** | width after grind, profile wear and weight matched |
| **Reversible inserts** | edges usable and chipped edges |
| **Bandsaws** | width after grind, set after service and weld condition |
| **Chains** | cutters remaining, stretch and damaged links |
| **Coated batches** | weight, surface area, pieces and masking required |

A trade no seeded family describes honestly, such as gauges for calibration, installs none and the preset says so rather than borrowing the nearest shape.

### What a family changes today

A preset installs its families switched off, and the workspace has no screen to edit a family, switch one on or give an item its family. So the inspection form asks for the service's own parameters, and the family choices in the Rules and Costing views are empty.

> Switching the preset off keeps its families, with their history.

## The registry and the item lifecycle

URL: https://kabaido.ai/docs/service-centre/the-registry-and-item-lifecycle

Register a customer's item, read its code and move it from arrival to return.

Why: The same tool comes back, and only a lasting identity tells you what has already been done to it.
What: Every item you service is a record in the registry with one code, a docket, labels and its full history.
How: Register it at `/app/servicing`, then move it on with the one action its row offers.

### Register an item

1. On the Work view choose **Register item**.
2. Under **What is it**, pick **Choose from the catalogue** or **Not in the catalogue** and describe it.
3. Set the **Service**, the **Customer** and, if it has one, **Max services**, then **Register**.

**More** then **Register from an order** (or **New job**) registers an order's lines at once: say how many items each line represents and which service they run through, and the customer, the description and the product come across. Each item then links back to the order.

### The code

An item's code is its serial: your **Serial prefix**, the year if you include it and a sequence, such as `ABC-26-00147`. Set the prefix under **Document IDs** in [Settings then Organisation](/docs/areas/settings#organisation); numbers already issued never change.

The same code family marks other traced things with a type letter after the prefix: B for batch, P for package, J for job, D for delivery, L for stock lot and O for order line. A code with no letter, or with I, reads as an item.

The drawer prints it three ways: **Print docket** (A6, with the QR and the customer), **Label 100x50** and **Label 62x29**. The QR opens `/t/<code>`; the Code 128 line carries the bare code for a wedge scanner.

### The lifecycle

| Status | The one next action |
| --- | --- |
| **Registered** | **Book in**. Booking in sets the due date from the service's turnaround. |
| **Intake** | **Inspect**. |
| **Inspection** | **Record inspection**. |
| **Awaiting approval** | **Chase approval**: the customer decides on the quote portal. |
| **In service** | The next bench's scan. **Mark complete** once every bench on its route is done or skipped. |
| **Completed** or **Rejected** | **Send back**. |
| **Returned** | **Service again** starts the next cycle on the same code. |

### Lifetime and limits

At **Max services** the item reads **Lifetime reached**, and booking it in again needs an engineer's **Override and book in**, recorded on the timeline. A measurement outside the serviceability **Limits** asks the inspector to **Mark not serviceable** or **Service anyway**.

**Mark not serviceable** is permanent end of life: the item stays in the registry for its history and **Reinstate** is the only way back.

### The drawer

Open any row for **Overview**, **Steps**, **Cost**, **History**, **Documents** and **Links**. History holds every status move and every station scan, with who made it.

Interactive example: One item's code as a Code 128 line and a QR, beside the trail behind it.

## The work list and inspection

URL: https://kabaido.ai/docs/service-centre/the-inspection-queue

See what needs doing first, reprice an item on what was found and ask the customer when the price moves.

Why: A board shows where every item is but never which one to pick up next.
What: The Work view ranks every open item and puts the one action that moves it on the row.
How: Open `/app/servicing`, work down **What needs doing** and inspect from the item.

### The Work view

| Block | What it shows |
| --- | --- |
| **What needs doing** | Every open item, ranked, with its reason in words and its next action. |
| The status strip | Counts per status. Choose one to filter the registry to that stage. |
| **Jobs in progress** | Open service orders with their station, promise and forecast. |
| **Stations** | The queue at each station in minutes against its capacity. |

### How the ranking works

1. Past the date promised back, most overdue first.
2. Due within three days, soonest first.
3. Everything else, longest waiting first.

Inside a band, work nearest to going out ranks higher: finished but not sent back comes first. An item with no due date sits in the last band; a due date comes from the service's **Turnaround** when the item is booked in.

### Inspect an item

1. Choose **Inspect** on the row, then **Record inspection**.
2. The form is pre filled from what was quoted. Correct it against the real item.
3. Choose **Recalculate**. The service's own formula prices what was measured.

### When the price moves

On a service marked **Subject to inspection**, a new price further from the quoted one than **Inspection approval delta (%)** in [Settings then Organisation](/docs/areas/settings#organisation) goes to **Awaiting approval**.

1. The customer contact is emailed a table of old against new, with a link to the quote portal.
2. They approve or decline there. Approve moves the item to **In service**; decline sends it back.
3. **Copy the approval link** resends it by hand.

Inside the threshold the new price stands and the item goes straight to **In service**.

### Reject

**Reject item** takes a reason (**Cracked**, **Undersize**, **Not economical** or **Other**), a note and an optional photo. The customer is notified; the item's line on a draft quote is voided, and a line on a quote already sent is marked rejected.

> Every move writes an event with who made it, so an approval, a rejection or an override can always be traced afterwards.

## Rules and customer preferences

URL: https://kabaido.ai/docs/service-centre/rules-and-customer-preferences

Find every workshop setting in one place and record what each customer has agreed.

Why: Terms agreed on the phone live in one person's head until they are written where everyone can see them.
What: The Rules view holds the workshop's settings, and each customer record holds what that customer has agreed.
How: An administrator sets rules at `/app/servicing?view=rules` and a customer's terms on their record at `/app/customers/[id]`.

### The Rules view

Each rule shows its sentence, its value, an **On** or **Off** switch and who overrides it. A preset's rules arrive **Off**.

| Rule | Group | What it says |
| --- | --- | --- |
| **Not economical** | Thresholds | Ask the customer when the service costs more than this share of a new one. |
| **Urgent surcharge** | Pricing lines | Add this to a job marked urgent. |
| **Rework at no charge** | Pricing lines | Price a rework for our own fault at nothing, and keep its cost. |
| **Minimum batch** | Defaults | Propose a batch at or above this count. |
| **Always confirm** | Confirmations | Always ask the customer in these cases, whatever their other rules say. |
| **Default value** | Defaults | Seed a parameter this customer always wants. |
| **Per tool or per batch** | Defaults | Register these as one tool each, as a set, or as a batch. |
| **Marking** | Pricing lines | Charge for putting an id on an item that arrived without one. |
| **Packaging** | Pricing lines | Charge for packaging we supply, at cost plus this markup. |
| **Compliant return discount** | Pricing lines | Reward a customer who keeps sending items back in good order. |
| **Prices at collection** | Visibility | Show prices on the rep's phone at the kerb. |
| **Re-price threshold** | Thresholds | Ask the customer when the measured price moves further than this from the declared one. |
| **Standing approval** | Confirmations | Cover a change without asking, up to what the customer has agreed. |

A rule can be overridden for a customer or a service, and the row says how many of each take it as it stands.

### A customer's terms

1. Open the customer at `/app/customers/[id]` and find the **Servicing** panel.
2. Set **Confirm before work**, **Pre approved up to**, **Scrap without asking below**, **Budget**, **Register as** and **Prices at collection**, or leave each on **Use your workspace**.
3. Add **Their own limits**, the **Collection day and cadence** and **Signature required**, then **Save terms**.

Each field shows the value in force today and where it comes from. Sales can read the panel and set the plain facts; the terms that change the workflow are set by an administrator.

> The Rules view and the customer's terms record what has been agreed; they do not change a price. What stops or warns on a price today is the service definition's own **Block** and **Warn** rules, and what sends a repriced item for approval is **Inspection approval delta (%)** in Settings then Organisation.

## Stations and scanning

URL: https://kabaido.ai/docs/service-centre/stations-and-scanning

Set up a bench as a station, sign a device in with its key and record work by scan.

Why: Work recorded later from memory is work recorded wrongly.
What: A station is a bench, a machine, a dock or a van with its own device key and one screen.
How: Add it in Settings then Organisation, sign the device in at `/station` and scan every handover.

### Add a station

1. Open `/app/settings/organisation?tab=stations` and choose **Add station**.
2. Give it a **Name**, an **Area**, a **Kind**, its **Station group** and its **Centre**, then **Add**.
3. Copy the device key. It is shown once and never again.

**Rotate key** signs the old screen out on its next scan. **Deactivate** ends the station and keeps its trail.

### Sign a device in

On the device, open `/station`, enter the **Device key** and **Sign in**. A station signs in, not a person, and it reaches its own screen and nothing else.

| Station | Its screen |
| --- | --- |
| Kind **Scan point** | `/app/scan`: resolve any code and record what happened to it. |
| Area servicing | `/app/servicing/station`: the steps waiting at that bench. |
| Kind **Van** | `/app/route/drive`: the day's run. See [the driver station](/docs/route/the-driver-station). |
| Kind **Machine** | `/app/machinist/station`: that machine's queue. See [machines and stations](/docs/machinist/machines-and-stations). |

A member of operator rank or above can open `/app/scan` in their own session, and a member who holds a station opens it from the rail.

### Scanning

Scan with a wedge scanner, choose **Use the camera** or type the code. With no signal, scans are held on the screen and sent in order when it returns.

A scan point may record **Registered**, **Received**, **Booked in**, **Marked**, **Station in**, **Station out**, **Packed**, **Counted**, **Moved** and **Step**. A code the workspace does not know offers **Register this code** or **Add as an alias of the next code**, so a customer's own number resolves to your item.

### The servicing station screen

The screen works through the steps written for each item at that bench: **Scan the item** shows the work required, the limits and the standard time, **Done** records the step and **Hand back** returns the item to inspection with a note. The station never sees a price.

Items do not carry written steps today, so the drawer's **Steps** tab reads **No workflow has been written for this item yet** and this screen has nothing waiting. Record the work by scan at a scan point and with the item's own actions at `/app/servicing`.

### Station groups

A station group is a class of work, not a place. Each station belongs to one, and a centre skips the groups it does not run.

| Station group | Applies to |
| --- | --- |
| Goods in | Everything that arrives |
| Cleaning | Everything |
| Inspection in | Everything |
| Marking | Anything the org marks |
| Bar sawing | Bar and rod cut to length for a new tool |
| Body work | Saw bodies |
| Tooth replacement, carbide | Carbide saws and cutters |
| Tooth replacement, diamond | Diamond saws, cutters and bits |
| Tip cutting | Diamond and carbide tips cut from a blank by wire or laser |
| Saw grinding | Circular saws |
| Diamond erosion | Diamond tooling |
| Rotary tool grinding | Drills, bits, endmills and hoggers |
| Knife and insert grinding | Knives and inserts |
| Bandsaw and chain | Bandsaws and chains |
| Coating | Anything coated, often subcontracted |
| Balancing and run out | Large blades and cutters |
| Inspection out and packing | Everything |
| Ready and loading | Everything |

## Cost against time

URL: https://kabaido.ai/docs/service-centre/cost-against-time

Set the rates and standard minutes that turn workshop time into cost, and read the reports.

Why: A price with no cost behind it cannot tell you whether the job made money.
What: Rates say what an hour, a tooth or a box costs you; standard minutes say how long a step should take.
How: At `/app/servicing?view=costing` an administrator sets the rates and an engineer or above the standard minutes.

### Rates

Choose **Add a rate**. Each rate applies to **The whole organisation**, one centre or one station, from a date. **Replace** starts a new figure without rewriting last month's costs.

| Rate | What it is |
| --- | --- |
| **Labour an hour** | What an hour at the bench costs you, fully loaded. |
| **Machine an hour** | What an hour on this machine costs, set per station where they differ. |
| **Driver an hour** | What an hour of a driver's time costs on a collection or a delivery. |
| **Overhead** | The share added to every job for the cost of being open. |
| **Packaging a package** | What a box, a sleeve or a crate costs you. |
| **Van a kilometre** | What a kilometre on your own van costs, shared over what it carried. |
| **Grinding wheel a tooth** | Wheel wear per tooth ground. |
| **Diamond tip a tooth** | What one diamond tip costs you. |
| **Braze a tooth** | Brazing material per tooth replaced. |
| **Wire a metre** | Erosion wire by the metre. |
| **Material a kilogram** | Bulk material by weight, for a batch process. |
| **Coverage a square metre** | What covering a square metre costs, for coating and finishing. |
| **Braze alloy a gram** | What a gram of silver braze foil costs you. |
| **Flux a tool** | What the flux for one brazed tool costs you. |
| **Subcontract a job** | What sending the work out costs, per job. |

Kabaido assumes no rate. A cost that needs a rate you have not set stays empty and says which one is missing.

### Standard minutes

**Add a figure** sets setup minutes plus run minutes for each count of its driver, for a station group and optionally for one service. The driver is **Per tooth**, **Per knife**, **Per piece** or **Once per item**. Figures from a preset are marked **Illustrative** until you replace them.

### How an item is costed

```text
item cost = steps (minutes x labour rate + minutes x machine rate + consumables)
+ packaging + run share
+ overhead per cent x everything above
margin = line price - item cost
```

Standard cost is the same arithmetic on the standard minutes, so variance shows at every level. Money is worked in minor units and rounded half up once, at the end.

### Reports

| Report | What it answers |
| --- | --- |
| **Cost and margin** | Standard against actual, by step, station, service, family, centre, customer or month. |
| **Lead time** | Door to door hours from the scans, as a median and the slowest tenth. |
| **Identification** | How many items arrived with your id, a brand reference or nothing. |
| **Tool life** | Services each item has had, what is left and when it is next due. |
| **Quality** | Rework by reason, station group, centre or month, with what it cost. |
| **Customers** | Items, quotes, decisions and revenue by customer, rep, route or quarter. |

Pick a period, **Run** and **Export CSV**. Costs and margins are engineer and above; other roles see minutes, lead times and identification.

> Actual minutes and cost are recorded step by step at the servicing station screen. Items do not carry written steps today, so an item's **Cost** tab reads **Nothing has been costed on this item yet** and **Cost and margin** and **Quality** come back empty. **Lead time**, **Identification**, **Tool life** and **Customers** read the registry and the scans.

## Batches through the AI

URL: https://kabaido.ai/docs/service-centre/batches

Send a customer's list of items to the AI and get every row priced against your services.

Why: A service enquiry arrives as a box and a list, and pricing forty lines by hand takes the morning.
What: The AI prices each line against your own service definitions, the same engine the bench uses.
How: Paste or attach the list in the one AI input at `/app`, in **Request** mode.

### Send a batch

1. Open `/app`, choose **Request** (or **Order** for a purchase order) and paste the list or attach the file.
2. Each line is matched to a service and its parameters are filled from what the customer wrote.
3. The answer is a **Service batch** card: line, description, serial, quantity, price and state.

| State | Means |
| --- | --- |
| **OK** | Priced by your formula. |
| **Needs info** | A parameter the price needs was not stated. It is asked for, never guessed. |
| **Rejected** | A **Block** rule stopped it, and the row carries that rule's message. |

### Act on it

- **Quote these items** drafts a quote from this card's rows. Rejected rows are left out.
- **Register items** gives every row without a serial its own code and books it into intake.
- A line that names a known serial loads that item's history, and its row shows how many times it has been serviced.
- A price on a service subject to inspection stays provisional until the item is measured at the bench.

### Questions about your items

In **Question** mode the same input answers "What has been done to item ABC-26-00147?" and "What is due for service this week?" from your registry.

> Each row is priced by the same engine that runs in the builder. Pricing a batch draws on your plan's usage; see [how usage works](/docs/billing/how-usage-works).

## Custom and paid setup

URL: https://kabaido.ai/docs/service-centre/custom-and-paid-setup

Install a ready made service model for your trade, or ask for one built to order.

Why: Most service trades share a shape, so most workshops should not start from a blank page.
What: A service centre preset installs a whole model; work no preset covers is built to order.
How: Turn a preset on in `/app/settings/presets`, or book a scoping call for anything else.

### Ready made

Each preset in the **Service centres** group installs its services, a centre, its families, a route through the station groups, illustrative standard minutes and its rule defaults. Every preset is free on every plan; its services count against your plan's [service allowance](/docs/service-centre/service-models-and-workflow-types), and one that does not fit is reported as **Not added**.

| Preset | Workflow type | Families |
| --- | --- | --- |
| **Tool regrind and recoat** | Product servicing | Shank tools |
| **Saw sharpening and retipping** | Product servicing | Circular saw blades and Bandsaws |
| **Blade and knife regrind** | Product servicing | Planer and profile knives and Reversible inserts |
| **Wheel re-profiling and balancing** | Product servicing | Bore cutters and hoggers |
| **PCD re-tip and regrind** | Product servicing | Shank tools and Circular saw blades |
| **Hob sharpening and recoat** | Product servicing | Shank tools |
| **Toolholder restoration and balancing** | Product servicing | Shank tools |
| **Calibration and certification** | Product servicing | None, and it says why |
| **Coolant management** | Site visit | None, and it says why |
| **Surface treatment and metal finishing** | Batch process | Coated batches |

### After installing

1. Put your own rates into each service at `/app/servicing?view=services`, then choose **Switch this service on** from its row's menu.
2. Replace the illustrative standard minutes with your own in the Costing view.
3. The preset's rules arrive **Off** in the Rules view. Switch on the ones that record how you work.

Switching a preset off pauses what it installed and deletes nothing: an item that went through a service keeps that history.

### Built to order

A service model for work no preset covers is quoted per project, with no published range, and runs on every plan once it is live. See [pricing](/pricing) and [work quoted per project](/docs/billing/work-quoted-per-project).

1. Choose **Book a scoping call** from the custom build panel in `/app/settings/presets`, or [contact us](/contact).
2. Bring your price list, a job sheet or a photograph of the form you use today.
3. The build is quoted before any work starts.

# Docs: Machinist

## Machinist

URL: https://kabaido.ai/docs/machinist

Machinist runs the floor and tells you what the job cost.

Machinist runs the floor and tells you what the job cost.

It can give the operator a screen built for that machine, with machine modules for tool grinding, plasma profiling, wire EDM and CNC milling, then schedule the jobs, machines and operators above them, track progress piece by piece and collect the time and material each job consumed.

Give your customers a lead time based on real capacity, and the status of their own production order without them having to ask.

Work arriving from a quote becomes a job, the job carries its trace code through every station, and the cost comes back against the order.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Machinist puts a screen built for the machine at the machine, through a machine module for plasma profiling, wire EDM, CNC milling or tool grinding, and runs a manufacturing execution system over them: jobs, machines, operators, a schedule and real costs. There is one job model, one station sign in, one cost model and one trace code across every machine module. Material a run consumes is written to the stock ledger, and the Stock area shows it when Stock is on. With [Commerce](/docs/commerce) on, a customer sees the status of their own production order and nothing else.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Machinist](/docs/areas/machinist) | `/app/machinist` | a full screen workbench |
| [Scan](/docs/areas/scan-station) | `/app/scan` | a station screen |

It adds to [Stock](/docs/areas/stock) when the product that brings that area is on too.

Works with [Stock](/docs/stock). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Machinist workbench with your machine modules, the Production view on Orders, machines, operators, the schedule and costs.

Switched off: Jobs, parts and machine setups stay readable. Nothing new can be nested, queued or run until it is switched on again.

### Who uses it

- Production Manager
- Works Manager
- Shop Floor Supervisor
- CNC Programmer
- Setters and Operators
- Production Planner

### The machine modules

| Machine module | For | Installed by |
| --- | --- | --- |
| [Arcline](/docs/machinist/arcline) | CNC plasma and sheet metal | The **Plate profiling and cutting** preset |
| [Wire EDM](/docs/machinist/wire-edm) | Wire EDM erosion | The **PCD and diamond tooling** preset |
| [CNC Milling](/docs/machinist/cnc-milling) | CNC milling, 3 plus 2 capable | The **PCD and diamond tooling** preset |
| [Tool grinding](/docs/machinist/tool-grinding) | Grinding solid carbide round tools | The **Solid carbide tool making** preset |

Install a preset from `/app/settings/presets`. A machine or process no machine module covers is scoped and built to order: choose **Talk about a custom build** on `/app/machinist` when nothing is switched on, or [contact us](/contact). It is quoted per project: see [work quoted per project](/docs/billing/work-quoted-per-project).

### The whole shop

| View | Route | What it holds |
| --- | --- | --- |
| [Machines](/docs/machinist/machines-and-stations) | `/app/machinist/machines` | Every machine as a station, its rate and its load today |
| [Operators](/docs/machinist/operators) | `/app/machinist/operators` | The people, their certifications and their rates |
| [Schedule](/docs/machinist/the-schedule) | `/app/machinist/schedule` | A day or a week board per machine |
| [Costs](/docs/machinist/costs) | `/app/machinist/costs` | What each finished job cost, standard against actual |

## Jobs

URL: https://kabaido.ai/docs/machinist/jobs

Know where a job comes from, how it moves and how its minutes are measured.

Why: A shop that cannot say where a job is or what it took cannot cost it.
What: A job is one unit of work at one machine, the same shape in every machine module.
How: The machine modules raise jobs as they plan work; a job moves by scans at the machine and carries a trace code from start to finish.

### Where a job comes from

| Raised when | Machine module | Standard minutes from |
| --- | --- | --- |
| A nest is approved or cut | Arcline | The nester's own time estimate |
| A run is queued or started | Wire EDM and CNC Milling | The run's modelled minutes from the chart |
| You ask the [AI interface](/docs/platform/the-ai-interface) to make a job and confirm the action it offers | None (a manual job) | Nothing: it has no standard minutes and no machine |

A nest or a run is exactly one job: approving the same nest twice raises one. Nothing on the machine module screens changes; the job simply sits behind the nest or the run.

### How a job moves

| Status | Means |
| --- | --- |
| Queued | Where every job starts: waiting on a machine, on the [schedule](/docs/machinist/the-schedule) |
| Draft | Taken back off the queue |
| Setting up | Setup minutes are being measured |
| Running | Run minutes are being measured |
| Paused | Stopped; a pause is not counted |
| Done, Scrapped or Cancelled | Finished; the job does not move again |

The moves happen on the [station screen](/docs/machinist/machines-and-stations) at the machine: **Take this job**, **Start setting up**, **Start running**, **Pause**, **Finish** and **Scrap**. Each move closes or opens the time segment and writes the trace event in one step; a pause or a finish also records the minutes on the costing ledger.

### Minutes are measured, not typed

A job's actual minutes are the sum of its setup and run segments from the scans. Open a job from the schedule or the costs to see its **Time** and its **Trail**.

1. Open the job from `/app/machinist/schedule` or `/app/machinist/costs`.
2. Under **Correct the minutes**, pick **Setup** or **Run** and enter the minutes.
3. Say what happened in **Why they are being corrected** and choose **Save**.

> A correction is stored as its own row, marked **Typed in**, with the reason. The scanned rows stay as they were. Corrections need the engineer role or above.


## Machines and stations

URL: https://kabaido.ai/docs/machinist/machines-and-stations

Add a machine, sign its screen in and read what it did today.

Why: The operator works from the screen at the machine, so the machine has to be something that screen can sign in as.
What: Every machine is a station with its own device key, its available minutes and its hourly rate.
How: Add it in `/app/machinist/machines`, then sign the screen at the machine in with the key.

### Add a machine

1. Open `/app/machinist/machines` and choose **Add machine** (administrators and owners).
2. Fill **Machine name** and pick the **Machine module** that raises its work, or none.
3. Set **Available minutes a day**, which the schedule plans against, and **Rate an hour, in pence**, which costs its time. Choose **Add**.
4. Write the device key down: it is shown once. **Issue a new key** later signs the old screen out.

A machine tied to a machine module also appears on that machine module's own Setup view.

### The screen at the machine

Open `/station` on the machine's screen and enter the **Device key**. The screen shows that machine's queue and the job on it now, and nothing else. A member who holds the machine among their stations, or an administrator, can open `/app/machinist/station` under their own sign in or pick the machine from **Stations** in the menu.

> Moves made while the signal is down are held on the screen and sent when it returns.

### Reading the list

| Column | Shows |
| --- | --- |
| **On it now** | The job in progress, or **Nothing on it** |
| **Minutes today** | Minutes measured by scans today |
| **Utilisation** | Those minutes against the available minutes you set; **Not known** until both exist |
| **Rate an hour** | The machine rate, or **No rate** when none is set |

### Stations and your plan

Stations are counted per workspace, across every station kind: a servicing bench and a delivery van count too. **Add machine** is disabled at the allowance, and reaching it never stops a screen already running.

| Plan | Stations included |
| --- | --- |
| Free | 1 |
| Pro | 2 |
| Ultra | 5 |
| Max | 15 |
| Enterprise | By agreement |

See [plans and usage](/docs/billing/plans-and-usage) to change plan.


## Operators

URL: https://kabaido.ai/docs/machinist/operators

Certify people for machines and see who is on what.

Why: A job should only move to a machine the person on it is trained to run.
What: The Operators view lists the members who work at stations, what each is certified for and what an hour of their time costs.
How: Certify a member for a machine in `/app/machinist/operators`; the schedule checks the certification before a job moves to another machine.

### Certify someone for a machine

1. Open `/app/machinist/operators` and choose **Certify for a machine** (engineers and above).
2. Pick the **Operator** and the **Machine**, set **Certified** and, if it lapses, **Expires**.
3. Choose **Save**. **Withdraw** on a certification removes it.

A certification is a capability, not a permission: the member's role still decides what they can see. Give someone the operator role in [Settings then Users](/docs/areas/settings#users).

### What the columns say

| Column | Shows |
| --- | --- |
| **Certified for** | Each machine, marked **Expired** or **Expires within thirty days** where it applies |
| **Rate an hour** | The person's labour rate, or **No rate**; engineers and above only |
| **On today** | The job they have open now |
| **Minutes this month** | Their measured minutes since the first of the month |

> An expired certification counts as none: the schedule refuses to move that person's job onto the machine.

## The schedule

URL: https://kabaido.ai/docs/machinist/the-schedule

Order the work on each machine and see what is late or over capacity.

Why: A lead time is only honest when it comes from what each machine can actually do.
What: The schedule is a day or a week board with a lane per machine and each open job as a block sized by setup plus standard minutes.
How: Put the jobs in the order you want; the board works out where each one ends against the machine's available minutes.

### Reorder the work

1. Open `/app/machinist/schedule` and pick **Day** or **Week**.
2. Drag a block within its lane, or use **Move up the queue** and **Move down the queue**.
3. To change machine, drag the block onto another lane or use **Move to a machine**.

Jobs with no machine sit in the **No machine** column. They are listed, not planned, until you move them onto one.

### What the board tells you

| Marker | Means |
| --- | --- |
| **Late** | Planned to finish after the job is due |
| **Over capacity** | More planned minutes than the machine's available minutes |
| **Not known** | The machine module gave no estimate, so the block adds nothing to the load |
| **ends 1h 55m into the day**, for example | How far into the working day the job ends. Not a clock time: nothing records when your day starts |

A machine with no **Available minutes a day** plans nothing; set it on [Machines](/docs/machinist/machines-and-stations).

> The board is the order you set. Nothing reorders it on its own: there is no solver and no AI, and the same jobs always give the same board. Moving a job onto a machine its operator is not certified for is refused.

## Costs

URL: https://kabaido.ai/docs/machinist/costs

Read what a finished job cost and where the figure is incomplete.

Why: A quote is only as good as what the last job really cost.
What: The Costs view prices each finished job from its measured minutes, the machine and labour rates and the material it consumed.
How: Open `/app/machinist/costs`, pick the dates and read by job, machine, operator or month.

### How a job is costed

| Part | Worked out as |
| --- | --- |
| **Machine** | The machine's hourly rate over the measured minutes |
| **Labour** | The operator's hourly rate over the same minutes |
| **Material** | What the run consumed, at the moving average cost on the stock line |
| **Job cost** | The three added together |
| **Margin** | The order line price less the job cost, where the job carries an order line |

**Standard** and **Actual** set the planned minutes against the measured ones. Open a row to see the job's time and trail. Rates carry an effective date, so a rate rise does not rewrite last month.

### Read it

1. Open `/app/machinist/costs`. It lists the done and scrapped jobs in a window that ends today.
2. Change **From** and **To** for another window.
3. Switch between **By job**, **By machine**, **By operator** and **By month**.

### When a figure is missing

- **No rate**: the machine or the person has no rate, so that part is left out and the total is what is known.
- No margin: a margin needs the order line a job was raised from, and the jobs the machine modules and the AI interface raise carry none.
- An Arcline job shows no material: the ledger records a cut against the sheet, not the job.

> Costs and margins are for engineers and above. A missing figure is shown as missing, never as a zero.

## Arcline

URL: https://kabaido.ai/docs/machinist/arcline

Run Arcline, the CNC plasma and sheet metal machine module, from parts library to cut file.

Why: In profile cutting the offcut is stock, and it only gets used if it is a record.
What: Arcline is the machine module for CNC plasma and sheet metal: parts, sheet stock and remnants, cut orders, nesting and the cut file.
How: Install the **Plate profiling and cutting** preset; opening Machinist then goes straight to Arcline's Shop view.

Screenshot of /app/machinist/arcline: The Arcline machine module in Machinist, turned on by the plate profiling preset: the four set up steps, the cut orders, the nest queue and the shop, all empty before the first job.

### The five views

| View | Holds |
| --- | --- |
| **Shop** | Open cut orders and what is due, the nest queue by material and thickness, low sheet stock and the activity trail |
| **Parts** | The parts library; each part opens in a 2D editor |
| **Orders** | Cut orders: the parts and quantities to cut, per customer |
| **Nest and cut** | The queue, the sheet canvas, the simulation and the export as G-code or DXF |
| **Setup** | Machines, sheet stock and remnants, and the cut chart (feed, pierce and kerf per material and thickness) |

The toolbar carries the counts that matter from any view (open orders, parts waiting to be nested, sheet stock below threshold), each a link to the view that clears it, and **New** offers **New part**, **New cut order** and **Nest the queue**.

### The loop it closes

1. A part is drawn from a template, in the editor or from a DXF, on a thickness the cut chart covers.
2. A cut order collects parts and quantities.
3. **Nest and cut** lays the parts onto a real sheet or a banked remnant and simulates the result.
4. Approving or cutting the nest raises its [job](/docs/machinist/jobs), with the nester's time as its standard minutes. Approval locks the layout and the cut settings, so the cut files export exactly as approved; a change is a new nest.
5. Completing the cut consumes the sheet and books the usable remnant back into stock.

> A part can only be drawn on a thickness that has a cut chart row. Add the row in **Setup** first for a material the shipped chart does not cover.

### Where the work comes from

A designed product with connected stock, such as a PCD saw blade body, raises a queued cut order when an order is created for it. See [rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

### Machines and your plan

Arcline's **Setup** holds its active machines to your plan's station allowance. See [machines and stations](/docs/machinist/machines-and-stations).


## Wire EDM

URL: https://kabaido.ai/docs/machinist/wire-edm

Run the wire EDM machine module: tip and knife profiles, erode orders, a queue with modelled wire times and the discs tracked as stock.

Why: PCD erodes slowly, so a shop needs to see what the week holds before it promises a date.
What: One place for what you erode, who it is for and how long the wire will take.
How: Install the **PCD and diamond tooling** preset and open Wire EDM from the Machinist switcher.

### The five views

**Shop**, **Parts**, **Orders**, **Erode** and **Setup**. The toolbar counts parts waiting to be eroded and disc stock lines below threshold.

### Parts

A part is a profile to erode, from a designed product, a DXF path or entered dimensions. It carries the material and the layer it is cut from, which the time model needs.

### Orders and the queue

An erode order collects profiles and quantities for one customer. In **Erode**, tick the waiting lines, pick a machine and choose **Queue the erode run**: the run carries a modelled wire time from the erosion chart and raises its [job](/docs/machinist/jobs). A line the chart cannot cover has no time and says so, and a run with such a line carries no total rather than a partial one.

### Stock

PCD discs and carbide blanks are stock lines with their real dimensions. Completing a run books them out; a run that uses more than is held writes a shortfall line rather than stopping at zero.

### The erosion chart

**Setup** holds the modelled wire feed per diamond layer plus the start and thread time. These are starting values to calibrate against your own machine. The estimate abstains beyond the thickest charted layer.

### Where the work comes from

A designed product with connected stock raises a queued erode order when an order is created for it, so a PCD saw blade sold through a quote arrives as profiles to erode. See [rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

## CNC Milling

URL: https://kabaido.ai/docs/machinist/cnc-milling

Run the CNC milling machine module: machined parts with modelled cycle times, machining orders, a run queue and billet stock.

Why: Cutter bodies are machined from billet, and the time on the machine is most of their cost.
What: One place for what you machine, who it is for and how long it will take on the machine.
How: Install the **PCD and diamond tooling** preset and open CNC Milling from the Machinist switcher.

### The five views

**Shop**, **Parts**, **Orders**, **Run** and **Setup**. The toolbar counts parts waiting to be machined and billet stock lines below threshold. The machine kinds cover a 3 axis vertical centre, a 3 plus 2 vertical centre and a horizontal centre.

### Parts and cycle times

A part comes from a designed product or entered dimensions and carries a modelled cycle time: a removal rate per ISO material group and a non productive allowance, both editable in **Setup**. Batch setup is charged per distinct part, not per piece.

### Orders, the queue and stock

Machining orders collect parts and quantities per customer. In **Run**, tick the waiting lines, pick a machine and choose **Queue the machining run**, which raises the run's [job](/docs/machinist/jobs). Round billets and blocks are stock lines with their real dimensions. Completing a run books the billets out; a run that uses more than is held writes a shortfall line.

### What is modelled

Every time here is modelled from published machining theory and your own chart rows: a planning number you make your own in **Setup**. Nothing here posts a program; your CAM system still produces the code.

### Where the work comes from

A designed cutter body with connected stock raises a queued machining order when an order is created for it. See [rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

## Tool grinding

URL: https://kabaido.ai/docs/machinist/tool-grinding

Run the tool grinding machine module: the factory order, each grinder's wheel pack and the grind, section by section.

Why: A designed tool has to reach the grinder with its rod, its wheels and its process settled.
What: One place for the grinders, their wheel packs and the orders a design raises.
How: Install the **Solid carbide tool making** preset, set up a grinder in **Setup** and open Tool grinding from the Machinist switcher.

### The four views

**Shop**, **Orders**, **Grind** and **Setup**. There is no Parts view: the tool is a design, and each order carries its own plan. The toolbar counts orders waiting to be ground and wheel and fluid lines at their reorder point.

### The factory order

An order opens as a page you can print: the tool, the rod and how many blanks it gives, the grinder and why, the wheel set with the pack drawn and the plan laid over it, the fluid, the process in order with its minutes, the steps off the machine and the measurement plan. The minutes are the quote's own. Download the tool definition as JSON for your own grinding software.

### Grinding

In **Grind**, pick the order. The checklist shows what is not ready with a one click fix: mount a wheel, top up the tank. Start the order, tick each section as it is ground, then complete it with the minutes it took and the first off readings. Completing books the rods out of stock and raises each wheel's tool count.

### Setup

**Machines** adds a grinder, draws its wheel pack and lets you mount, take off, retire or dress a wheel and top up the tank. **Wheels** and **Fluids** list what the toolroom holds, with the quantities Stock counts in the store and on each machine.

### What is not modelled

Kabaido does not solve the grind. It gives the wheel set and the process, and your own grinding software expands the order into paths. Wheel life, dressing intervals and removal rates are not published for diamond on carbide, so none is predicted.

### Where the work comes from

A quoted endmill sent to the factory from the [solid carbide endmill](/design-engineer/solid-carbide-endmills) design module, or an order that contains one. See [rates, stock and the machine bridge](/docs/design-engineer/stock-modes).

# Docs: Wizard

## Wizard

URL: https://kabaido.ai/docs/wizard

Wizard picks the right product for the application, the way an application engineer would.

Wizard picks the right product for the application, the way an application engineer would.

It can ask what the user actually knows, the material, the workpiece, the machine and what matters most on the job, compute the correct specification from published engineering data, then rank your own catalogue against it alongside a 3D view of the answer.

Give your customers a specification they can act on in a minute, with your products at the end of it.

It is deterministic. No AI is used per run, so the same answers give the same recommendation every time.

Run it internally or embed it on your own website. On your customer surface, a run arrives as a quote request.

Wizards exist for bandsaw blades, PCD saw blades, coating selection and machining tools. New ones are built to order.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Engineering logic compiled from published manufacturer guidance, sourced and dated, turns what the user knows into a full specification, then matches it to the organisation's own catalogue, or to its services for a coating, with a 3D view of the answer where the wizard draws one. No model call happens on a run, so the same inputs always give the same answer, and every line names the chart it came from. It runs for the team in the workbench, for signed in customers on the customer facing surface when Commerce is on, where a run becomes a quote request, and embedded on the organisation's own website, where a run shows in the wizard's activity and raises no quote request.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | an area in the menu |
| [Wizard](/docs/areas/wizard) | `/app/wizard` | a full screen workbench |

Works with [Commerce](/docs/commerce). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Wizard workbench with your wizards, the embed for your own website and quote requests from runs on your customer surface.

Switched off: Past runs stay readable. The wizards and the embed stop answering until it is switched on again.

### Who uses it

- Internal Sales
- Technical Sales
- Applications Engineer
- Marketing
- The organisation's own customers on the website

### The wizard modules today

| Wizard module | Answers | Comes with the preset |
| --- | --- | --- |
| [Bandsaw blade](/docs/wizard/bandsaw-blade) | Pitch, family, width, band speed and loop length | Saw blades |
| [PCD saw blade](/docs/wizard/pcd-saw-blade) | A diamond tipped circular blade and its running data | Saw blades; PCD and diamond tooling |
| [Coating and treatment](/docs/wizard/coating-selector) | The process family for a corrosion target | Coatings and surface treatment; Surface treatment and metal finishing |
| [Machining tool](/docs/wizard/machining-tool) | The tool and the cutting data for a cut | Cutting tools; Indexable tooling |

A wizard for something not listed is [built to order](/docs/wizard/custom-wizards).

### Runs and usage

- The free plan allows 10 wizard runs a calendar month in the platform, and the toolbar shows how many are left. Paid plans have no run cap.
- Runs on your website and by signed in customers do not count towards that cap.
- Every run draws a small activity measure from the one [usage pool](/docs/billing/how-usage-works). A spent balance never stops a run.

## The bandsaw blade wizard

URL: https://kabaido.ai/docs/wizard/bandsaw-blade

Read the published reference tables the bandsaw blade wizard computes from.

Why: A blade recommendation you can trust names the chart behind it.
What: It computes pitch, blade family, width, band speed and loop length, then ranks your bandsaw blades against them.
How: The tables below are the engine's own data, exactly what it reads.

Screenshot of /app/wizard/bandsaw-blade: The bandsaw blade wizard at its first step: the material question, the 3D cut in the centre and the specification waiting for the answers.

> Every value is a published starting point, tuned at the machine. Outside a table the wizard says so.

### Materials

Thirteen materials drive the blade family and the speed. Stainless asks its grade and tool steel its condition, as the charts split on them.

| Material | Blade families, ranked | Note |
| --- | --- | --- |
| Mild steel | Bi-metal (M42 tooth edge); Carbide tipped (TCT) | Bi-metal M42 carries general mild steel work; carbide earns its keep on high production. |
| Stainless steel | Bi-metal (M42 tooth edge); Carbide tipped (TCT) | Bi-metal M42 first; carbide offered for production runs. |
| Aluminium | Bi-metal (M42 tooth edge); Carbide tipped (TCT) | Bi-metal covers general aluminium; carbide for production on purpose built saws. |
| Titanium | Bi-metal, high tier (M51 class production ranges); Carbide tipped (TCT) | High tier bi-metal (M51 class) first, then carbide. |
| Tool steel | Bi-metal (M42 tooth edge); Carbide tipped (TCT) | Annealed tool steel cuts on bi-metal; hardened tool steel needs carbide. |
| Cast iron | Bi-metal (M42 tooth edge); Carbide tipped (TCT) | Bi-metal for machined iron; carbide for scale and chill. |
| Hardwood | Carbon steel (flexback and hardback); Sawmill and resaw; Bi-metal (M42 tooth edge) | Carbon for general work, resaw bands for deep sections, bi-metal wood ranges for abrasive or reclaimed timber. |
| MDF and chipboard | Carbon steel (flexback and hardback) | Carbon fine pitch for man made board. |
| Foam | Bandknife | Knife edges: straight, wavy or scallop. No teeth. |
| Insulation | Bandknife | Knife edges: straight, wavy or scallop. No teeth. |
| Leather | Bandknife | Knife edges: straight, wavy or scallop. No teeth. |
| Glass and ceramics | Grit and diamond | Grit and diamond only; no conventional teeth. |
| GRP and composites | Grit and diamond | Grit and diamond, including carbide grit ranges. Dust extraction required. |

Family branches follow the Addler hardness tiers and the Dakin-Flathers M42 and M51 guidance, accessed 2026-07-28.

### Pitch for solid sections

The engaged width picks the band whose centre is nearest, then the nearest standard pitch. The why line says which.

| Section width | TPI |
| --- | --- |
| 0-5 mm | 18 |
| 4-8 mm | 14 |
| 2-15 mm | 10/14 |
| 8-20 mm | 8/12 |
| 16-30 mm | 6/10 |
| 25-40 mm | 5/8 |
| 35-70 mm | 4/6 |
| 60-120 mm | 3/4 |
| 80-200 mm | 2/3 |
| 120-400 mm | 1.5/2 |
| 250 mm and up | 1.1/1.6 |
| 400 mm and up | 0.75/1.25 |

Source: Addler (Excision) bandsaw blade tooth selection guide, accessed 2026-07-28.

### Pitch for tubes, pipes and profiles

Rows are section width W, columns wall thickness T, both in mm; cells are TPI. An empty cell is outside the chart, and the wizard says so.

| W (section) | T 1 | T 1.6 | T 2 | T 2.5 | T 3 | T 4 | T 5 | T 6 | T 7 | T 8 | T 9 | T 10 | T 12 | T 15 | T 20 | T 50 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 10 mm | 14 | 10/14 | 10/14 |  |  |  |  |  |  |  |  |  |  |  |  |  |
| 20 mm | 14 | 10/14 | 10/14 | 10/14 | 8/12 |  |  |  |  |  |  |  |  |  |  |  |
| 25 mm | 14 | 10/14 | 10/14 | 10/14 | 8/12 | 8/12 |  |  |  |  |  |  |  |  |  |  |
| 30 mm | 14 | 10/14 | 10/14 | 10/14 | 8/12 | 8/12 | 6/10 |  |  |  |  |  |  |  |  |  |
| 40 mm | 14 | 10/14 | 10/14 | 10/14 | 8/12 | 8/12 | 6/10 | 5/8 | 5/8 | 5/8 |  |  |  |  |  |  |
| 50 mm | 14 | 10/14 | 10/14 | 8/12 | 8/12 | 6/10 | 6/10 | 5/8 | 5/8 | 5/8 |  |  |  |  |  |  |
| 60 to 120 mm | 14 | 10/14 | 10/14 | 8/12 | 8/12 | 6/10 | 6/10 | 5/8 | 5/8 | 4/6 | 4/6 | 4/6 | 4/6 | 3/4 | 3/4 |  |
| 130 to 150 mm | 10/14 | 10/14 | 8/12 | 8/12 | 6/10 | 6/10 | 5/8 | 5/8 | 4/6 | 4/6 | 4/6 | 4/6 | 3/4 | 3/4 | 3/4 |  |
| 150 to 180 mm | 10/14 | 8/12 | 6/10 | 6/10 | 5/8 | 4/6 | 4/6 | 4/6 | 4/6 | 4/6 | 4/6 | 3/4 | 3/4 | 3/4 |  |  |
| 190 to 300 mm | 6/10 | 6/10 | 5/8 | 4/6 | 4/6 | 4/6 | 4/6 | 4/6 | 4/6 | 3/4 | 3/4 | 2/3 |  |  |  |  |
| 350 to 400 mm | 4/6 | 4/6 | 3/4 | 3/4 | 3/4 | 3/4 | 2/3 |  |  |  |  |  |  |  |  |  |
| 450 to 500 mm | 4/6 | 4/6 | 3/4 | 3/4 | 3/4 | 3/4 | 2/3 |  |  |  |  |  |  |  |  |  |

Source: Addler (Excision) tooth selection guide, corroborated by the Shark Bandsaw Blades UK wall by diameter matrix, accessed 2026-07-28.

### Blade width and minimum contour radius

Straight cuts want the widest blade the machine takes; contour cuts the widest that still turns the radius.

| Blade width | Minimum radius |
| --- | --- |
| 3 mm (1/8") | 5 mm (3/16") |
| 5 mm (3/16") | 8 mm (5/16") |
| 6 mm (1/4") | 16 mm (5/8") |
| 10 mm (3/8") | 38 mm (1 1/2") |
| 13 mm (1/2") | 64 mm (2 1/2") |
| 19 mm (3/4") | 140 mm (5 1/2") |
| 25 mm (1") | 180 mm (7") |

Source: Ravenview bandsaw blade radius chart, corroborated by the Dakin-Flathers width guide, accessed 2026-07-28.

### Band speed starting ranges

Metres per minute, bi-metal blades unless noted. Silver curled chips are right, powdery chips mean feed too low, blue chips mean speed or feed too high.

| Material group | Start range m/min | Notes |
| --- | --- | --- |
| Free machining steels (EN1A, 12L14, 1215) | 90 to 105 |  |
| Low carbon and structural (S275, A36, EN3, 1018) | 60 to 80 |  |
| Medium carbon (EN8, 1045) | 60 to 72 |  |
| High carbon (EN42, 1080, 1095) | 50 to 60 |  |
| Alloy steels (EN19, 4140 class) | 50 to 70 |  |
| Bearing and spring (52100, 6150, 5160) | 45 to 60 |  |
| Stainless austenitic 304 | 30 to 45 |  |
| Stainless 316 and duplex | 25 to 40 | Start at the lower end of the range. |
| Tool steels annealed (D2, H13, O1) | 20 to 40 |  |
| Hardened steel above 45 HRC | 20 to 40 | Cut with carbide only and follow the blade maker. |
| Grey cast iron | 40 to 60 | Can be cut dry. |
| Aluminium alloys | 80 to 300 | The top of the range is machine dependent: 84 to 104 m/min is a conservative bi-metal production range, and carbide on a purpose built saw runs far higher. |
| Copper | 60 to 90 |  |
| Brass | 65 to 110 |  |
| Bronze alloys | 35 to 90 | Depends on the alloy. |
| Titanium | 15 to 25 |  |
| Nickel superalloys (Inconel, Hastelloy) | 10 to 20 | Carbide preferred, on a rigid setup. |
| Wood on carbon blades | see note | Follow the machine plate. Woodworking band speeds run far higher than metal, typically tens of metres a second. |
| Glass, ceramics and composites on grit bands | see note | Run a low band speed for the machine and follow the blade maker. |

Source: Blade Serpent per alloy speed chart and the Emin Academy family chart, accessed 2026-07-28.

### Wood pitch guidance

Each depth takes the coarsest standard pitch inside the Dakin-Flathers rule of three to six teeth in the workpiece.

| Depth of cut | TPI |
| --- | --- |
| under 15 mm | 10 to 14 (finish work and tearout control) |
| 15-40 mm | 6 to 8 |
| 40-90 mm | 4 to 6 |
| 90-180 mm | 3 to 4 |
| over 180 mm | 3 (or a dedicated resaw or sawmill band where the machine takes 27 mm and up) |

Source: derived from the Dakin-Flathers teeth per inch rule, accessed 2026-07-28.

### Other sources

Blade break in follows Starrett, corroborated by Cutting Tool Engineering and Canadian Metalworking. Radius cutting practice follows Saw Service of Washington.

## The PCD saw blade selector

URL: https://kabaido.ai/docs/wizard/pcd-saw-blade

Specify a diamond tipped circular blade from the machine, the material and the cut quality, with every line naming its table.

Why: Panel and composite blades are specified from published tables, not from memory.
What: The PCD saw blade wizard module returns diameter, bore, kerf and plate, tooth count, tooth form, hook angle, spindle speed and feed.
How: Give it the machine class, the material and your priority; each result line names its table in a why popover.

### What it asks for

- The machine class, which sets the typical diameter, bore and stack.
- The material, which sets the tooth form, the hook angle and the tip material.
- The blade diameter, bore, stack height and spindle limit where you know them, and the priority: balanced, finish or tool life.

### Where it abstains

- The published dimension table covers 300 to 450 mm. Outside it, kerf, plate and tooth count are a starting point to confirm, not a published value.
- Aluminium and plastics tooth counts are carried from the published band by pitch, and outside 250 to 400 mm scaled by diameter; both say so.
- A diameter outside what the machine class commonly runs warns and names the range.
- A spindle speed below the material's rim speed band warns, with the true rim speed printed.
- On a beam saw, the scoring blade is paired with the main blade by the published pairing rule.

### Sources

Published manufacturer and distributor guidance: machine class tables, the tip material ladder, the dimension tables, tooth count bands, tooth form and hook angle by material, rim speed bands, the chip load and feed formula and the scoring pairing rule.

## The coating and treatment selector

URL: https://kabaido.ai/docs/wizard/coating-selector

Rank the process families that meet a corrosion target on a given substrate, with the ISO 10683 designation where one resolves.

Why: A coater's first question is which process a part should go through and what the specification should say.
What: The coating and treatment wizard module ranks the process families that meet a corrosion target and states the route.
How: Give it the substrate, the environment and the target; it returns the families, the designation, the route and the add-ons to raise.

### What it returns

- The ranked process families, each with a sector typical salt spray reach for the coater to confirm.
- The designation, where one resolves: a full ISO 10683 code for zinc flake, built only from the published classes.
- The process route, barrel, rack or spray, with the reason.
- For fasteners, the add-on services to raise, and for every job the pricing drivers captured for the quote.

The salt spray classes are exactly the published set: 360, 500, 720, 1000 and 1500 hours to red rust. No designation is ever minted beyond the top class, and a reach that is a sector norm is labelled as an estimate.

### What it matches

Your services, not your catalogue: coating is work done on the customer's parts. The recommended process is matched to the services set up in [Servicing](/docs/areas/servicing), and once the reader gives the batch weight, area or piece count a service prices on, your own rate card prices it. A figure the rate card needs and has no default for is asked for rather than guessed, and any default it assumes is shown.

> Hydrogen embrittlement is a rule, not a footnote: a high tensile steel part warns and is steered away from electrolytic processes towards zinc flake or mechanical plating, which are hydrogen free.

## The machining tool selector

URL: https://kabaido.ai/docs/wizard/machining-tool

Turn a machining job into the tool to use and the cutting data to run it at, then rank your own cutting tools against it.

Why: A tooling customer asks what to use for a job and what to run it at.
What: The machining tool wizard module returns the tool specification and the cutting data together, then ranks what you hold against it.
How: Describe the part, the material, the machine and the cut; every result line names its table.

### What it asks for

- The part: a block or billet, a plate, a round bar, a tube or a casting or forging, and its size.
- The material, one of sixteen the published cutting data covers, with its condition where that changes the answer.
- The machine and the operation: nine milling operations, seven turning operations and seven ways of making a hole.
- Only the cut figures that operation needs, the finish for a finishing pass, and the machine's speed and power.

### What it returns

- The tool: diameter, flutes, coating, corner and reach for a solid tool, or the ISO 1832 designation, nose radius, grade, chipbreaker and entering angle for an indexable one.
- The cutting data: speed, spindle speed, feed, table feed, depth and width of cut, removal rate, power and torque.
- The setup: climb or conventional, entry, coolant, pecking, passes and workholding.
- The warnings the cut earns, from a spindle that cannot pull it to an excluded coating.

### How it reads a published table

A published feed carries the chip thinning of its row's engagement. At a different engagement the selector takes the feed back to the row's chip thickness and forward to yours, rather than quoting it across unchanged.

### Where it abstains

No published row, no speed: for example solid carbide slotting in hardened steel, or high speed steel in aluminium, titanium or the nickel alloys. It states no tool life in minutes; it reports what a change of speed costs in life, which the Taylor exponent supports. Where publishers disagree, it names the one it used and says they disagree, rather than averaging them.

### What it matches

It reads end mills, drills, reamers, inserts and holders across their schemas and scores each against its own kind. Holders follow the inserts, because a holder is the accessory rather than the answer.

> **Have this one made to order** opens the design workbench with the whole specification set, so a tool you do not hold can be quoted as a special.

The **Cutting tools** preset installs the selector with its schemas. See [Kabaido for cutting tool makers and distributors](/cutting-tools).

## Embedding a wizard

URL: https://kabaido.ai/docs/wizard/embedding-a-wizard

Put a wizard on your own website with an embed key and one iframe.

Why: A visitor gets a specification on your own site and your team sees the run.
What: An embed key serves one wizard, against your catalogue, inside an iframe on your website.
How: The Kabaido team connects your site and sends the key; you paste one iframe into the page.

### Get a key

1. Open the wizard at `/app/wizard`, choose **Where it runs** in the rail, then **Get the embed**.
2. Ask the Kabaido team to connect your site, and name the wizard it should serve.
3. The team sends you the key, which starts `wze_`. Keep it with your site build.

| Rule | What it means |
| --- | --- |
| One key, one wizard | The key decides which wizard runs, not the page. The Kabaido team can change which wizard it serves. |
| One key per workspace | A workspace holds one active key at a time, so a second key means revoking the first. |
| Rotating | A new key replaces the old one at once, so the iframe needs the new key. |
| Revoking | The embed shows page not found and the wizard leaves your site. |

### Add the iframe

Paste this where the wizard should sit, with your key in place of `wze_YOUR_KEY`. The iframe does not resize itself, so give it room.

```html
<iframe
  src="https://kabaido.ai/embed/wizard/wze_YOUR_KEY"
  title="Product selector"
  loading="lazy"
  style="width: 100%; height: 1400px; border: 0;"
></iframe>
```

### What happens next

- The wizard matches your catalogue, or your services for the coating selector.
- Runs appear in the wizard's **Usage** and **Activity** panels as **Your website**, with one notification a day when the site is used.
- Product prices from your catalogue show; service prices stay hidden.
- A run on your website does not raise a quote request.

> The key is the protection: the embed page loads for anyone who has it. Signed in customers can run wizards on your customer facing surface instead, where a run becomes a quote request. That needs [Commerce](/docs/commerce/the-customer-surface).

## Custom wizards

URL: https://kabaido.ai/docs/wizard/custom-wizards

Know how a wizard for your own products is built to order and what it has to rest on.

Why: Your trade may select products from charts no current wizard module reads.
What: A custom wizard module is built to order from your engineering data and the published charts your trade works to.
How: Talk to the Kabaido team; the wizard is added to your workspace alone.

### Ask for one

1. Open `/app/wizard`. With no wizard switched on, choose **Talk about a custom wizard**; otherwise [contact us](/contact).
2. Bring the charts, tables and rules you select by today, and the catalogue schema the answer should rank.
3. Kabaido quotes the build, then adds the wizard to your workspace, where it appears under **Switch wizard**.

### What every wizard keeps

- Deterministic: no AI per run, and the same inputs always give the same answer.
- Every line names its chart or rule, and says whether it is a published chart, derived from a published rule or practice guidance.
- Outside the published data it abstains and says so rather than extrapolating.
- Missing input asks a question or states its default.

### Price

A custom wizard is one-off work quoted per project, with no published range. See [work quoted per project](/docs/billing/work-quoted-per-project).

# Docs: Inspect

## Inspect

URL: https://kabaido.ai/docs/inspect

Inspect tells your sales team which manufacturers to approach and what to say when they get there.

Inspect tells your sales team which manufacturers to approach and what to say when they get there.

It can map UK manufacturers into engineering grade profiles from public sources, what they make, what they run and what that implies they buy, then rank who to go to, say what to lead with and write the questions worth asking.

Give a prospect a conversation worth having, technical from the first minute, about the work they actually do.

Every data point carries its evidence, so nothing goes into a call that cannot be backed up.

Outreach runs through your own inbox, visits plan into routes, and every debrief folds back into a private view of your market.

Start free or book a walkthrough at kabaido.ai today.

### In more detail

Every manufacturer in a region is recorded, and each one with a public footprint is profiled from public sources, with evidence behind each data point and a grade for how much stands behind it. The organisation loads its offering map once. Inspect then ranks what to lead with, writes the questions to ask, sends a first touch through the organisation's own inbox and folds every debrief back into that organisation's private view. It is not a data broker and not a volume sender: the difference is engineering inference, offering context and question generation.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Inspect](/docs/areas/inspect) | `/app/inspect` | a full screen workbench |

It adds to [Customers](/docs/areas/customers) when the product that brings that area is on too.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Inspect workbench with the mapped regions, lists, the planner, companies and campaigns, and turning a company into a customer.

Switched off: Your lists, notes and debriefs stay readable. No profile can be opened and no campaign can run until it is switched on again.

### Who uses it

- Area Sales Manager
- Field Sales
- Business Development Manager
- Internal Sales doing outbound
- Marketing

### The two layers

The **shared layer** is Kabaido's mapped regions, the same for every customer. Your **own layer** is private: activations, opened profiles, lists, the planner, campaigns, your offering map, contacts, documents and the facts your team captures. Nothing in your layer ever reaches another organisation.

### The views

| View | Where | For |
| --- | --- | --- |
| Region | `/app/inspect` | The county in a list or on a map: [the region](/docs/inspect/the-region). |
| Companies | `/app/inspect/companies` | Every company you are working: [companies and campaigns](/docs/inspect/companies-and-campaigns). |
| Lists | `/app/inspect/lists` | Named working sets: [lists and the planner](/docs/inspect/lists-and-the-planner). |
| Planner | `/app/inspect/planner` | The run of visits and follow ups: [lists and the planner](/docs/inspect/lists-and-the-planner). |
| Campaigns | `/app/inspect/campaigns` | Email sequences to the contacts you hold: [companies and campaigns](/docs/inspect/companies-and-campaigns). |
| Offering | `/app/inspect/offering` | What you lead with: [the offering map](/docs/inspect/offering-and-documents). |
| Company | `/app/inspect/company/[id]` | One profile, its contacts and its documents: [opening profiles](/docs/inspect/opening-profiles). |

## The growing map

URL: https://kabaido.ai/docs/inspect/the-growing-map

Know how a county is mapped, what the public figures mean and how to ask for your county next.

Why: A map that claims more than it holds is worse than no map, so every figure is read from the records themselves.
What: Kabaido maps manufacturers one ceremonial county of England at a time, and the public [Inspect page](/inspect) shows the map as it grows.
How: Read the figures on [the Inspect page](/inspect), open a live county in `/app/inspect`, or request the county you sell into.

### How a county is mapped

- Every manufacturer registered or operating in the county is recorded, anchored on its Companies House number where one exists.
- Each company is looked for on the web. One with nothing beyond the register and basic directory listings stays recorded but sits outside the **verified set**, and the workbench does not list it.
- Every profiled value is **verified** (a source states it, and the source is cited) or **inferred** (derived, with the reasoning written down). Missing stays missing.
- What is recorded is measured against the official count of manufacturing sites in the county, so the gap is a number too.

### The stages of a county

| Status | Means |
| --- | --- |
| **Planned** | On the list to map next. |
| **Mapping** | Being researched and imported now. |
| **Live** | Mapped and counted. Its figures join the public page. |

Every executed county import ships a Kabaido release, and the county records the version it arrived in. The public list shows a live county as "added in" that version.

### The public figures

The figures come from `/api/stats/inspect`, which reads `inspect_regions` alone and nothing at company level. [The Inspect page](/inspect) renders them through the same reader, so the two cannot disagree.

| Figure | Read from |
| --- | --- |
| **Counties live** | The regions whose status is live. |
| **Companies mapped** | Every company recorded in the live regions. |
| **Verified sites** | The verified set in the live regions. Shown only when every live region carries the count. |
| **Profiles with evidence** | The profiles in the live regions graded **Full profile**: a verified website plus corroborating sources. |
| **Latest county** | The live region mapped most recently, by name and date. |

> A figure that is zero or not yet counted is left off the page, never shown as zero.

### Request your county

1. Open [the Inspect page](/inspect) and find **Request your county** beside the map.
2. Choose the **County**, then enter your **Company** and a **Work email**.
3. Press **Request this county**. It is posted to `/api/contact`, the contact form's own route, so it reaches Kabaido as a lead, you get a confirmation email and we reply by email. It does not add the county to the map by itself.

## The region

URL: https://kabaido.ai/docs/inspect/the-region

Activate a county, then find the companies worth working in its list or on its map.

Why: A rep works a list and uses a map to get their bearings, so the region offers both from one switch.
What: The Region view at `/app/inspect` shows every verified company in an activated county, with enough to judge which are worth opening.
How: Choose the region in the header, switch between **List** and **Map**, then narrow it with the segments and **Filters**.

Screenshot of /app/inspect: The Inspect workbench on its Region view: a county's summary and what is in it by trade, before a region is activated.

### Activate a region

A county you have not activated shows its totals only. An admin or owner activates it with the button that reads **Activate** and the county's name; how many regions a workspace holds at once is agreed with us.

### Find companies

1. Open `/app/inspect` and pick the county from the region menu in the header.
2. Pick a segment, or **Suits what you sell** to keep the segments your presets fit.
3. Open **Filters** for local authority, size, process on site, likely demand, where you are with them and list membership.
4. Search by name, trade or process, then use **Add to a list** on any row worth keeping (it appears once you have a list).

### What a row shows

Name, kind, local authority, staff band and the evidence counts (processes, machines, materials, certifications, signals, named people), with an **Open** badge on the profiles you have already opened and your engagement status once you have set one.

The count line gives the verified companies in the county, and a second line says how many more are recorded with nothing beyond the register. None of this draws on your usage.


### The map

**Map** plots the same companies, clustered until you zoom in. Choose a pin to see the company and open its profile. A row's **Show on the map** jumps straight to it.

**Export** beside **Filters** downloads every company you have opened as a CSV. See [what Inspect draws on your usage](/docs/inspect/billing).

## Coverage and evidence

URL: https://kabaido.ai/docs/inspect/coverage-and-evidence

Read a profile the way it was built: graded tiers, cited evidence and honest gaps.

Why: Nothing should go into a call that cannot be backed up.
What: Every profiled value carries its basis and its sources, and every profile is graded by how much evidence stands behind it.
How: Open a profile, then choose any value to see where it came from.

### Profile tiers

| Tier | What stands behind it |
| --- | --- |
| **Full profile** | A verified website plus corroborating sources. |
| **Standard profile** | A website or a directory profile. |
| **Stub** | Register and premises data only. Nothing is invented about the operation. |

Many of a county's smallest manufacturers leave no usable web footprint, so stubs are expected and labelled rather than padded.

### Verified and inferred

- **Verified**: a source states it. The source, the quote and the date it was read are one click away.
- **Inferred**: derived from what is stated, with the reasoning written down.
- Missing: left empty and listed under **What we do not know yet**, never a guess.


### What a profile holds

| Tab | Holds |
| --- | --- |
| **Profile** | Processes, machines, materials, certifications, sectors, scale, the MRO demand profile, the written narrative with numbered sources, and **Your intelligence**. |
| **Commercial** | Filed employees and turnover with an as of date, accounts filed and due, charges, Gazette notices and dated signals. |
| **Contacts** | People named publicly, your stored contacts and the [contact finders](/docs/inspect/connectors). |
| **Prepare** | The documents, the debrief, where this stands and the activity. |

> County court judgments are not free to search, so the Commercial tab says they are unavailable rather than implying a clean record.

## Opening profiles

URL: https://kabaido.ai/docs/inspect/opening-profiles

Know what is free, what opening a profile draws on and what the free plan shows.

Why: Planning who to look at should never cost anything; reading the evidence is the part worth paying for.
What: Browsing is free, and opening a company's full profile draws on the month's usage once, the first time.
How: Press **Open profile** on a company page; everything you open stays open to you.

### Open a profile

1. Choose a company in `/app/inspect` to reach its page. The panel **What is behind this profile** says what opening it reveals.
2. Press **Open profile**. The four tabs appear, and the **Contacts** tab can now find people through a connected [contact finder](/docs/inspect/connectors).

### What it draws on

- Opening a company draws on the month's usage about as much as one AI answer.
- A profile you have opened stays open to you for good, so reading it again never draws anything.
- The map, the list, the filters, search, your lists and the planner never draw on anything.

When the month's usage is spent, no new profile opens. The region, your lists and every profile you have already opened carry on, and opening resumes on your billing date or on a larger plan.

### On the free plan

Inspect is on every plan. On the free plan the workbench is a preview: the header reads **Preview. Opening a company needs a paid plan.** with a link to **See plans**. The free plan's monthly profile cap is zero; it is a cap on use, not a gate on the product.

> Opening is always a deliberate press. Hovering over a list or a link never opens a profile or draws on your usage.

## Lists and the planner

URL: https://kabaido.ai/docs/inspect/lists-and-the-planner

Group the companies you mean to work, then run your visits and follow ups from one screen.

Why: A patch is worked in batches: the run on Tuesday, the accounts a branch covers, the names off a trade show.
What: Lists hold those batches, and the planner shows every company you are working in the order it is next due.
How: Build lists from the region, then set a status or plan a visit and the company joins the run in `/app/inspect/planner`.

### Make a list

1. Open `/app/inspect/lists` and press **New**. Name it after the patch it covers and press **Create**.
2. In `/app/inspect`, choose **Add to a list** on each company worth keeping.
3. Back in Lists, choose the list to see its companies and how many you have opened. **Export** downloads the opened companies on it as a CSV.

Adding a company to a list never opens its profile, so planning draws nothing. Deleting a list leaves its companies in the region.

### The planner

Every company with an engagement status, grouped by day and then by postcode district so a run makes route sense, with undated companies under **No date set** at the end. Each row carries its latest visit agenda.

| Edit in place | Values |
| --- | --- |
| Status | Researching, Contacted, Meeting, Visit planned, Visited, Opportunity, Customer, Parked |
| Owner | Any member of your workspace |
| Next action | A date |
| Notes | A working note |

Filter by owner, then **Print run sheet** for a paper copy. A company without an agenda offers **Prepare one**. **Plan visit** on a company page puts it on the run.


> Inspect sits beside your CRM, not instead of it: no forecast, no opportunity values and no second pipeline.

## Companies and campaigns

URL: https://kabaido.ai/docs/inspect/companies-and-campaigns

See where you are with every company you have worked, and build outreach sequences from your own inbox.

Why: The region tells you who is there; you also need to know where you stand with the ones you have touched.
What: Companies lists every company you track, and Campaigns holds short email sequences to their contacts.
How: Open `/app/inspect/companies`, select companies and act on them, or add them to a campaign in `/app/inspect/campaigns`.

### Companies

A company is tracked once it is on a list, its profile is open, you hold a contact, you logged an activity, it has an engagement or it is in a campaign. Columns: status, owner, next action, what you hold, campaign, customer and last activity.

- Row actions: **Open the company**, **Add to a list**, **Add to a campaign**, **Log an activity** and **Convert to customer**.
- Select several rows to **Add to a list**, **Add to a campaign** or **Set the owner** in one go.
- Filter by status, owner, region, list, campaign, opened, contacts and customer.

### Convert to customer

**Convert to customer** creates one customer record from the profile's name, website, email domain, trading address and company number, and copies your stored contacts that have an email. Evidence never becomes a customer field, and pressing it twice changes nothing.

### Campaigns

1. Press **New campaign**, name it, choose the inbox under **Sends from** and, if you have one, a list.
2. In **Setup**, choose what to **Lead with** from your offering map and the sending hours. An admin sets the pace per day.
3. In **Steps**, add each email with its delay, subject and message. **Merge fields** fill each one from the company and the contact.
4. In **Members**, add from a list or from a selection in Companies, then press **Start**.

A reply stops the sequence for that person, always. A member whose company needs consent under PECR, or whose address is suppressed, is shown as refused and never written to.

> The scheduled sender is not built yet. Starting a campaign queues its members, and nothing goes out on its own. A first touch sends today from a visit agenda: see [outreach and compliance](/docs/inspect/outreach-and-compliance).

## The offering map and the two documents

URL: https://kabaido.ai/docs/inspect/offering-and-documents

Load what you sell once, then prepare the visit agenda and the price list, both grounded in evidence.

Why: An agenda can only rank what you actually sell, so your side of the match comes first.
What: The offering map lists your products, services and value adds; the agenda and the price list are built from it and the profile.
How: Fill `/app/inspect/offering`, then use **Build a meeting agenda** or **Draft a price list** on an open company.

### Fill the offering map

1. Open `/app/inspect/offering`. With nothing saved, it shows a map drafted from your presets, product schemas, catalogue, services, design modules and wizards, each row saying where it came from.
2. Edit that draft, or press **Build this from what we sell** to have the AI interface draft one, or **Standard distributor menu** for a starting point.
3. Give each offering a **Value area**, the **Demand it answers** and its **Proof points**, then press **Save this map** (later, **Save offering map**).

The value areas are uptime, efficiency, cost saving, safety, sustainability, easy and efficient buying and working capital. **What this produces** previews the ranking against your latest opened company, free.

### The visit agenda

1. A site snapshot from the profile, cited.
2. Likely challenges, each graded known, inferred or assumed.
3. The top three solutions from your offering map, never more.
4. The questions to ask, specific to this site.
5. The departments and buying centres likely on site.
6. The way in: one credible opening line built on one cited specific.
7. What we do not know yet, as discovery targets.

**Build a meeting agenda** opens the AI interface at `/app` with the company in scope, and the agenda lands on the company's **Prepare** tab. Where the evidence is thin it abstains in front of you.

### The price list

**Draft a price list** selects lines from your own catalogue that match what the company is evidenced to do, with your quantity breaks and a suggested customer discount from its filed turnover, employees or size band. No model writes a line: the selection and the discount are deterministic, and the reasoning is printed so you can overrule it.

### Debriefs

After a visit or call, **Debrief this visit** on the **Prepare** tab opens the AI interface. Machines seen, people met and challenges heard become facts private to your organisation, shown under **Your intelligence** and winning over the shared value in your view.

## Contact finders

URL: https://kabaido.ai/docs/inspect/connectors

Connect the contact tools you already pay for in Settings and use them from an open profile.

Why: Your team already pays for a contact tool; Inspect should use it rather than sell you another.
What: Apollo and the other contact finders are integrations, each connected once on your own account.
How: Connect one in [Settings then Integrations](/docs/areas/settings#integrations), then find and reveal on a profile's **Contacts** tab.

### The finders

| Finder | Connect with | On the Contacts tab |
| --- | --- | --- |
| [Apollo](/docs/integrations/apollo) | OAuth, started by an admin or owner | Find and reveal |
| [Lemlist](/docs/integrations/lemlist) | An API key | Find and reveal |
| [Prospeo](/docs/integrations/prospeo) | An API key | Find and reveal |
| [Anymailfinder](/docs/integrations/anymailfinder) | An API key | Reveal only |
| [Clay](/docs/integrations/clay) | An API key and your table's webhook URL | Not searched: it works through pushes and callbacks |

The Hunter connection is written but not switched on yet, so it is not offered.

### Find and reveal

1. Open the company's profile, then its **Contacts** tab.
2. Choose the **Contact provider** and press **Find people** for a free, obfuscated preview.
3. Press **Reveal** on a person. It runs on your provider account, and the contact is stored once, whichever finder found them.

Find and reveal need an open profile and the sales role, work one company at a time and are rate limited per organisation.

### Connecting Apollo

- In Kabaido, only an admin or owner can start the connection.
- In Apollo, the person who approves it needs permission to authorise third party apps. Anyone else is sent back with a permission error.
- Apollo reports no balance through this connection, so check what is left in Apollo itself.

> Only the company name, the domain and, on a reveal, the person's name and title ever leave the platform through a finder. Profiles, evidence, your facts and your documents never do.

## Outreach and compliance

URL: https://kabaido.ai/docs/inspect/outreach-and-compliance

Send a grounded first touch through your own inbox, with the PECR guard and your suppression list enforced.

Why: A first touch is only credible when it names something true about the site, and only lawful when the rules allow it.
What: A visit agenda ends with one cited opening line, which you can send from your organisation's connected inbox.
How: Open the agenda on the **Prepare** tab, check **What goes out**, enter the recipient and press **Send from your inbox**.

The send carries your organisation's identification and an unsubscribe line, and it logs as an activity on the company. With no inbox connected, copy the text into your own client.

### The PECR guard

| Subscriber | Who | Marketing email |
| --- | --- | --- |
| Corporate | Limited companies, LLPs and plcs | Allowed without prior consent |
| Individual | Sole traders and non LLP partnerships | Needs consent first, so there is no send option |
| Not established | Legal form unknown | Treated as individual |

The guard runs on the server and applies to single sends and campaigns alike.

### The suppression list

Addresses or whole domains on the list are never written to by any Inspect send. An admin edits it under **Suppression** in a campaign's **Activity** panel, or at the **Outreach suppression** entry in [Settings then Integrations](/docs/areas/settings#integrations). An objection is honoured absolutely.

## What Inspect draws on your usage

URL: https://kabaido.ai/docs/inspect/billing

Know which Inspect actions draw on the month's usage and which are always free.

Why: Inspect is where activity is felt most, so you should know in advance what draws and what does not.
What: Inspect is on every plan and draws on the same monthly usage pool as the rest of your workspace.
How: Watch the bar in the Inspect header: your share of the month, and what you have opened, stored and exported.

### What draws and what is free

| Action | Draws on the month's usage |
| --- | --- |
| Open a company profile | About as much as one AI answer, once per company |
| Store a contact from a finder | The same as opening a profile, once per person |
| Build a meeting agenda | About twice that, because a model writes it |
| Draft a price list | The same as opening a profile |
| Debrief a visit | The same as opening a profile |
| Draft the offering map in the AI interface | The same as opening a profile, when a model drafts it |
| Export a CSV | A little for the file and a little per company in it |
| Browse, search, filter, lists, the planner, Companies, campaign setup, sending a first touch, reading an opened profile | Nothing |

The bar turns amber as the month runs low. When it is spent, the map, the lists and everything already opened carry on.

### Exports

An export covers the companies you have opened, with your debrief facts, your activity and an index of your documents; a list export adds the note written when each company went on the list. Every row carries a watermark and every export is audited.

> Inspect data is licensed for your internal business use: no resale, no redistribution and no loading into third party data platforms beyond the identity fields a finder receives.

How many regions you hold at once is agreed with us. Distributor fleets and multi team territories belong in an [Enterprise](/docs/billing/enterprise) agreement.

# Docs: Commerce

## Commerce

URL: https://kabaido.ai/docs/commerce

Commerce puts your catalogue online as a B2B trade site and connects it to the platform.

Commerce puts your catalogue online as a B2B trade site and connects it to the platform.

It can sell your catalogue records, turn registered accounts into your customers and drop their orders straight into the platform with your numbering, your pricing and your VAT, so there is no second system to keep in step.

Give your customers a place to buy, reorder and check their own account at any hour, built to be found by people and by the AI search that increasingly answers technical questions for buyers.

A build is quoted per project, publicly stated at £6,500 to £12,500, and the site then runs on your ordinary Kabaido subscription.

Book a walkthrough at kabaido.ai today.

### In more detail

Commerce gives your customers their own branded sign in, where each one sees only their own quotes, orders, items, deliveries, designs, wizards and documents, with a customer AI you can switch on. The same surface can run on your own domain. With a website build, the site sells your own catalogue records, registered accounts become customers matched by contact email, and website orders become platform orders with platform numbering, your VAT rate and the ordinary order workflow. The area opens on **Customers online**; its **Website** view is the workbench for a built site: Overview, Content, Enquiries, Blog and Checklists.

### Where it lives

| Area | Where | Kind |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | `/app/quotes` | an area in the menu |
| [Orders](/docs/areas/orders) | `/app/orders` | an area in the menu |
| [Catalogue](/docs/areas/catalogue) | `/app/catalog` | an area in the menu |
| [Commerce](/docs/areas/commerce) | `/app/commerce` | a full screen workbench |

It adds to [Customers](/docs/areas/customers), [Servicing](/docs/areas/servicing), [Design](/docs/areas/design), [Wizard](/docs/areas/wizard) and [Route](/docs/areas/route) when the product that brings those areas is on too.

Works with [Design Engineer](/docs/design-engineer), [Route](/docs/route), [Service Centre](/docs/service-centre) and [Wizard](/docs/wizard). Nothing is a prerequisite: each pair only adds to the other.

### Switching it on and off

Switch it on in [Settings then Products](/docs/areas/settings#products), on any plan. It brings the Commerce workbench, the customer facing surface where your customers sign in to their own quotes, orders and items, and orders from your site landing under Orders.

Switched off: Orders and enquiries from your site stay readable. Your customers cannot sign in and the site stops feeding the platform until it is switched on again.

### Who uses it

- Marketing Manager
- E-commerce Manager
- Internal Sales handling enquiries
- The organisation's own customers

### Three tiers

| Tier | Where your customers sign in | What it takes |
| --- | --- | --- |
| 1. [The customer surface](/docs/commerce/the-customer-surface) | `<prefix>.kabaido.ai`, or `kabaido.ai/c/<prefix>` on the Free plan | Commerce on, **Customer sign in** switched on and a prefix chosen: see [activating your address](/docs/commerce/activating-your-address) |
| 2. [Your own domain](/docs/commerce/your-own-domain) | A subdomain of yours, such as `portal.yourdomain.com` | One CNAME record, on Pro, Ultra and Max |
| 3. [The website build](/docs/commerce/the-website-build) | A trade website on your domain, feeding the platform | A build quoted per project, £6,500 to £12,500 |

> Without Commerce, the quote link at `/q/[token]`, the document link at `/doc/[token]` and the wizard embed still work. Commerce adds the signed in surface around them.

## The customer surface

URL: https://kabaido.ai/docs/commerce/the-customer-surface

Know what your customers see when they sign in, and at which address.

Why: Your customers ring to ask where an order is and what a quote said, and the answers are already in your workspace.
What: A branded sign in where each customer sees exactly their own records and nothing else.
How: Switch Commerce on, choose a prefix, then give each customer an access code.

### The two addresses

| Address | Form | Plans |
| --- | --- | --- |
| Path address | `kabaido.ai/c/<prefix>` | Every plan |
| Your Kabaido address | `<prefix>.kabaido.ai` | Pro, Ultra and Max |

Both open the same surface. On the Free plan the path address is the one you share.

### What a customer sees

| Area | Available when |
| --- | --- |
| Quotes, Orders and Documents | Always, because Commerce brings them |
| Items | Service Centre is on |
| Deliveries | Route is on |
| Designs | Design Engineer is on |
| Wizards | Wizard is on |
| Ask (the customer AI) | You switch it on: see [the customer AI](/docs/commerce/the-customer-ai) |

Each area also needs its own switch on in [Customer facing settings](/docs/commerce/customer-facing-settings). An area whose gate fails is simply not there.

The home page shows a card per open area: quotes awaiting a decision, orders in progress, items with you, deliveries in the next seven days and the newest documents. Every screen carries **Powered by Kabaido** in the footer.


## Customer facing settings

URL: https://kabaido.ai/docs/commerce/customer-facing-settings

Find every setting of the customer surface and know what each one does.

Why: The surface is yours to shape, and every change should be live without a deploy.
What: One settings page for the address, the domain, the brand, the areas and the customer AI.
How: Open `/app/settings/customer-facing`, change what you need and choose **Save**.

Screenshot of /app/settings/customer-facing: Settings then Customer facing: the customer sign in switch, the prefix with the path address and the Kabaido address, your own domain and the brand.

**Customer facing** appears under Settings when Commerce is on. Admins and owners can open it. Changes are live on the next load.

| Section | What it holds |
| --- | --- |
| Address | **Customer sign in** on or off, the **Prefix**, both addresses, **Activate address** and **View as a customer** |
| Your own domain | The **Domain**, the CNAME record to add and **Attach domain**: see [your own domain](/docs/commerce/your-own-domain) |
| Brand | **Logo**, **Icon**, **Wordmark**, **Brand colour** with a live preview and the **Default theme** |
| What customers can use | A switch per area, the wizard modules customers may run, **Customer AI**, **Messages a day per customer** and **Allow sign up** |
| Welcome and support | **Welcome title**, **Welcome text**, **Support email** and **Support phone** |
| Notifications to your customers | The access code invitation and the welcome email |
| What a public scan shows | How much a scan of one of your labels tells someone who is not signed in: see [traceability](/docs/parts/traceability) |

> Turning **Customer sign in** off keeps every row. Both addresses then show a page saying there is nothing at that address.

An area switch is greyed with its reason when its own product is off, for example **Needs Route** beside Deliveries. With **Allow sign up** off, only people who already redeemed a code can sign in.

## Activating your address

URL: https://kabaido.ai/docs/commerce/activating-your-address

Choose a prefix and bring your customer address live.

Why: Customers need one address to remember, in your name.
What: A prefix gives you the path address at once and your own Kabaido address on a paid plan.
How: Set the prefix in Settings then Customer facing and choose **Activate address**.

### Bring it live

1. Open `/app/settings/customer-facing`.
2. Switch **Customer sign in** on and type a **Prefix**: lower case letters, digits and single hyphens, not starting or ending with a hyphen. The field shows the length allowed.
3. Choose **Save**. The path address works from here on.
4. On Pro, Ultra and Max, choose **Activate address** for `<prefix>.kabaido.ai`.
5. Choose **View as a customer** to walk the surface as your most recently active customer, read only.

### The states

| State | Meaning |
| --- | --- |
| Not activated | Only the path address answers. |
| Activating | The platform is checking the address. This usually takes under a minute. |
| Ready | Links to customers use your Kabaido address, or your own domain once that is ready. |
| Failed | The address did not answer. **Retry** returns it to Activating. |

> Changing a ready prefix breaks saved links. The old prefix is kept on record so support can explain a dead link.

Some words are reserved (such as app, docs and shop) and a prefix must be unique across Kabaido.

## Branding

URL: https://kabaido.ai/docs/commerce/branding

Put your logo, icon and colour on the customer surface.

Why: It is your surface, so it should look like yours.
What: Your wordmark, icon and colour replace Kabaido's on every customer screen.
How: Upload the assets and set the colour under **Brand** in Settings then Customer facing.

| Setting | Where it shows |
| --- | --- |
| **Wordmark** | The top bar and the sign in card. Without one, your organisation's name is set in its place. |
| **Icon** | The browser tab icon. |
| **Logo** | Held with the surface's brand. The screens themselves show the wordmark. |
| **Brand colour** | Every use of blue on the surface, the buttons and the sign in gradient. |
| **Default theme** | Light, Dark or System. |

Upload a PNG, JPEG or WebP; SVG is refused. An uploaded asset has **Remove**.

A light brand colour is kept, not replaced: text on it switches to dark and the button uses the deeper tone. The **Preview** beside the colour shows the result.

An empty logo or colour falls back to the ones in [Settings then Organisation](/docs/areas/settings#organisation), which also brand your documents and email with or without Commerce.

> The Kabaido icon stays in two places only: the customer AI's mark and **Powered by Kabaido**, which is on every screen and every plan.

## Access codes and invite links

URL: https://kabaido.ai/docs/commerce/access-codes-and-invite-links

Give a customer's people a sign in, and take it away again.

Why: A code is the only way in, so nobody reaches a customer's records by guessing an address.
What: One active code per customer record, which links every person who redeems it to that customer.
How: Open the customer record's **Access** tab, create a code and send the invitation.

### Invite a customer

1. Open the customer at `/app/customers/[id]` and choose the **Access** tab.
2. Set a **Label**, **Expires** and **Maximum accounts** if you want limits, then choose **Create access code**.
3. Choose **Send invitation** and pick the contact under **Send to**, or copy the **Invite link** or the code itself and read it down the phone.

The invite link applies the code for them: they sign up with Google, Microsoft or email and never see a code field. Anyone else enters the code after signing in.

### Change or end access

| Action | Effect |
| --- | --- |
| **Rotate** | The old code stops working. People already signed in stay signed in. |
| **Revoke** | Nobody new can join until a new code is created. |
| **Remove** (on a person) | That person's sign in ends at once. They can join again with a valid code. |

Old codes are kept under **Previous codes**. **People signed in** lists who joined, how and when they were last seen; a website account that joined is marked **Storefront account**.

Members at Sales and above manage codes. A wrong code always reads "That code is not valid.", and repeated failures are refused for a while.


## The customer AI

URL: https://kabaido.ai/docs/commerce/the-customer-ai

Decide whether your customers can ask an assistant about their own account.

Why: Most customer questions are about their own quotes, orders and items, and the answers are already recorded.
What: An assistant on the customer surface that reads only that customer's own records.
How: Switch **Customer AI** on in Settings then Customer facing or on the Customers online view.

> It is off by default. Turning it on asks you to confirm, because customers' questions draw on your workspace's usage.

### What it can and cannot see

| It can | It never can |
| --- | --- |
| Read that customer's quotes, orders, items, deliveries and documents, where those areas are open | See your catalogue, costs, margins or pricing rules |
| Answer a technical question from what it can cite, or say it cannot see it | See another customer's anything |
| Raise a request with your team, which reaches you as a request and a notification | See your plan or your usage |

Every answer is charged to your organisation's usage, not to the customer. **Messages a day per customer** caps each person.

A person who reaches the cap reads that they have reached today's limit. When your usage runs out, they read only that the assistant is not available just now, with your support contact, and never why.

## What a customer can and cannot do

URL: https://kabaido.ai/docs/commerce/what-a-customer-can-and-cannot-do

Know exactly what a signed in customer can read and change.

Why: You open your system to people outside your company, so the edges must be plain.
What: A customer user is a separate kind of account, never a member of your workspace.
How: Every read is limited to rows that belong to their own customer record.

### A customer can

- Accept or decline a sent quote, with a purchase order reference or a reason.
- Follow orders, deliveries and serviced items, and answer an inspection waiting on them.
- Request a collection of a serviced item.
- Run the wizards you open to them and choose **Ask for a quote** on a result or a saved design.
- Download the documents addressed to them.
- Ask the customer AI, when you switch it on.
- Leave your workspace from **Account**, and see the other suppliers that gave them a sign in.

### A customer cannot

- See another customer's records, your catalogue, your costs or your margins.
- Open your workspace at `/app`: a customer account is never a member.
- Create a workspace from your address.
- Reach an area you have switched off, or one whose product is off.

Reading costs nothing. A request and a wizard run each draw a little of your usage, and never refuse the customer; the customer AI draws on it per answer.

## Customers online

URL: https://kabaido.ai/docs/commerce/customers-online

See who uses your customer surface and switch the customer AI on or off.

Why: You should know whether customers use the sign in you gave them.
What: The first view of the Commerce area: addresses, invited customers, live sessions and customer activity.
How: Open `/app/commerce`; it opens on **Customers online**.

Screenshot of /app/commerce: The Commerce workbench on its Customers online view before set up: the sign in not yet switched on, no customer invited and the customer AI off.

| Panel | What it shows |
| --- | --- |
| **Your customer sign in** | The path address, your Kabaido address and your domain, each with its state, plus **Customer facing settings** (admins) and **View as a customer** |
| **Customers invited** | Each customer with a code, how many people use it and their last sign in, with the count **Signed in this hour** above |
| **Customer activity** | What customers did, newest first |
| **Customer AI** | The switch and **Messages a day per customer** |

Every role with the Commerce area sees the view. Admins and owners can change the AI switch here; it saves at once.

With no customer invited yet, the view says so and points to the customer record's Access tab. **Website**, beside it, is the [website workbench](/docs/commerce/the-workbench).

## Your own domain

URL: https://kabaido.ai/docs/commerce/your-own-domain

Serve the customer surface on a subdomain of your own.

Why: Some customers trust an address in your own domain more than one in ours.
What: The same customer surface on a subdomain such as `portal.yourdomain.com`, with no website build.
How: Add one CNAME record pointing at `cname.kabaido.ai`, then attach the domain.

Available on Pro, Ultra and Max. On the Free plan the section says a paid plan can use its own domain.

### Attach it

1. In `/app/settings/customer-facing`, under **Your own domain**, type the **Domain** and choose **Save domain**.
2. Add the record shown (**Name**, **Type**, **Target**) at your DNS provider:
   ```
   portal.yourdomain.com CNAME cname.kabaido.ai
   ```
3. Choose **Attach domain** and wait. **Retry** any time.

### The states

| State | Meaning |
| --- | --- |
| Not attached | The domain is saved but not live. |
| Attaching | Waiting for the record to propagate and the certificate to issue. The surface answers there as soon as the record reaches us. |
| Ready | Verified and serving your surface. |
| Failed | The reason is shown. Fix the record and choose **Retry**. |

> Use a subdomain. An apex such as `yourdomain.com` cannot take a CNAME and is refused, as is any Kabaido host or a host your Commerce website already uses.

**Remove** detaches the domain. The path address and your Kabaido address keep working.

## The website build

URL: https://kabaido.ai/docs/commerce/the-website-build

Understand what a Commerce website build is, what it costs and how it starts.

Why: A trade website that does not know your catalogue or your customers is a second system to keep in step.
What: A B2B trade site on your domain that sells your catalogue records and feeds the platform.
How: Book a walkthrough, receive a written quote, and we build, connect and run it.

### What it costs

It is billed as two invoices and quoted per project, stated publicly at £6,500 to £12,500. Once live the site runs on your ordinary Kabaido plan, with no separate hosting line. See [pricing](/pricing).

### How it runs

1. Open `/app/commerce/website` and choose **Schedule a Commerce meeting**, or [contact us](/contact).
2. We go through your range, your customers and your current site, then quote the build in writing.
3. We build on a preview address, load your content and connect the site to your workspace.
4. On launch day we switch the site to your domain. `/app/commerce/website` then opens the workbench.

Until a site is connected, the Website view shows the workbench with sample data under glass.

Website accounts can reach the [customer surface](/docs/commerce/the-customer-surface) with an access code, matched by their email, so a buyer has one identity.

## The Commerce workbench

URL: https://kabaido.ai/docs/commerce/the-workbench

Work your managed site from the platform: live activity, the content the build is waiting on, enquiries, the blog and the launch checklists.

Why: The site is managed for you, but it is still your channel.
What: A full screen workbench over your connected site with five views.
How: Open `/app/commerce/website`; with a site connected it opens on **Overview**.

| View | What it gives you |
| --- | --- |
| **Overview** | Visitors, orders, enquiries awaiting and wizard runs, daily activity charted and a live feed |
| **Content** | Every text and image slot on the site with its state. See [content and photography](/docs/commerce/content-and-photography) |
| **Enquiries** | The queue of enquiries sent on the site. See [enquiries](/docs/commerce/enquiries) |
| **Blog** | What is published and what is planned, and **Add an idea** |
| **Checklists** | The launch and growth steps of your project and their state |

Checklist items read **Not started**, **In progress**, **Waiting on you** or **Done**. Waiting on you is the honest one: the build is blocked on something only you can give.

Every member with the area sees the workbench. Editing content, adding blog ideas and ticking checklist items need an admin; replying to enquiries needs Sales.


## How the site and the platform fit together

URL: https://kabaido.ai/docs/commerce/site-and-platform

Understand what is shared between your site and your Kabaido account, and what happens to an order placed online.

Why: A site with its own products, customers and orders is one more system to keep in step.
What: One product database, one customer list and one order book, all the platform's.
How: The site reads from your workspace and writes back into it through a connection we hold.

| On the site | In the platform |
| --- | --- |
| A product page | A catalogue record, including its price and specification |
| A registered account | A customer, matched by contact email, with any special pricing you have agreed |
| An order placed online | A platform order with your numbering, your VAT rate, documents and notifications |
| An enquiry form | An enquiry in the workbench queue |
| A product finder | A wizard, run against the same catalogue |

An order arrives only after the site's own payment is confirmed. A line whose SKU is not in your catalogue stays a manual line.

### Inviting your existing customers

On a customer record, **Invite to your website** emails their contact a link to create a trade account. Nothing else changes until they register.

### Length priced products

A catalogue product can be priced against one dimension, such as a length, with an add on and a minimum charge, so cut to size stock sells online without a configurator. A real configurator is a [Design Engineer](/docs/design-engineer) design module.

### The connection

The link is a key we mint and hold, not something you configure. A content edit is pushed to the site when you save it. If you leave, your catalogue, customers and orders are already in the platform: see [export your data](/docs/integrations/export-your-data).

## Content and photography

URL: https://kabaido.ai/docs/commerce/content-and-photography

See what the site's pages are waiting on and change their text yourself.

Why: A build is usually waiting on words or photographs, and that should be visible, not buried in email.
What: Every text and media slot on the site, page by page, with its honest state.
How: Open **Content** in the workbench at `/app/commerce/content`.

| State | Meaning |
| --- | --- |
| **Populated** | The image or video is in place. |
| **Awaited** | The project is still waiting on this shot; the row says which one. |
| **Pending publish** | A text edit is saved and on its way to the site. |

Filter by **Page**, **Kind** (Text, Images, Video) and **State**. The header counts slots populated, images still awaited and edits pending publish.

### Change a line of text

1. Find the text slot and choose its edit button (admins only).
2. Change the text and choose **Save**. It reads **Pending publish** until the site confirms it.

Photographs are real shots of your own products and premises, never stock images. They go to the project team, not through this screen.

> Products never appear in Content. A product on the site is a catalogue record: change it in the [Catalogue](/docs/areas/catalogue) and the site follows.

## Enquiries

URL: https://kabaido.ai/docs/commerce/enquiries

Answer and close the enquiries your website receives.

Why: An enquiry left in a web form inbox is a sale waiting on nobody.
What: A queue of every enquiry sent on your site, with reply and close built in.
How: Open **Enquiries** in the workbench at `/app/commerce/enquiries`.

Each enquiry is **New**, **Replied** or **Closed**, and you are notified when one arrives. The header says how many are awaiting a reply.

1. Open the enquiry and write your answer in the reply box.
2. Choose **Send reply**. It is emailed with their message quoted underneath, and stored on the enquiry.
3. Or choose **Close without replying** when nothing is owed.

Replying needs the Sales role or above. To quote, open a quote for the customer in [Quotes](/docs/areas/quotes) as for any other enquiry.


# Docs: Areas

## AI

URL: https://kabaido.ai/docs/areas/ai

Send a request, a purchase order or a question from the one input in the platform and find every thread again.

Why: Requests arrive as emails, POs and questions, and each needs the catalogue, the price and the engineering behind it.
What: One input for the whole workspace: paste a request, a purchase order or a question and get a cited answer.
How: The products you switch on decide what it can do; every chat stays under Recents in the menu.

Find it at `/app`: an area in the menu. Brought by every workspace.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Request | Paste or forward a request: it is matched, priced and kept as a thread. | Every workspace |
| Order | Paste a purchase order to check it against its quote and draft the order. | Sales Engineer, Design Engineer, Service Centre, Wizard and Commerce |
| Question | Ask a technical or catalogue question and get an answer that cites its source. | Every workspace |

### Parts you meet here

- [Customer context](/docs/parts/customer-context)
- [Activity](/docs/parts/activity)
- [Integrations](/docs/parts/integrations)

### The three kinds of message

| Choose | Send it | What comes back |
| --- | --- | --- |
| **Request** | An enquiry to price, an RFQ or a drawing. | Every line set out, matched against what you sell or service, then drafted into a quote. |
| **Order** | A purchase order. | Lines matched and checked against the quote they came from, then drafted into an order. |
| **Question** | A technical question or one about your own work. | An answer with its sources. |

### Send a request

1. Open `/app` and choose **Request** under **What you are sending**.
2. Paste the RFQ, attach it or describe what the customer needs, then choose **Send message**.
3. Read the answer in the thread. It is kept in the menu under **Recents** and opens again at `/app/r/<id>`.

**Question** is always offered. **Request** and **Order** appear only with a product that quotes, a role of sales or above and Quotes or Orders in your access, as [the AI interface](/docs/platform/the-ai-interface) sets out. Other areas link into it with a prepared prompt, such as **Ask about this customer** on a customer record, and nothing is sent until you send it.

## Quotes

URL: https://kabaido.ai/docs/areas/quotes

Draft, send and revise a quote, follow it through its statuses and see what the customer sees at the portal link.

Why: When quotes live in inboxes and spreadsheets, what is out, won or expiring is hard to see.
What: Every quote to a customer in one list, with the count and value at each stage.
How: Draft from a request or by hand, send the PDF with its portal link and track each answer.

Find it at `/app/quotes`: an area in the menu under Sales. Brought by [Sales Engineer](/docs/sales-engineer), [Design Engineer](/docs/design-engineer), [Service Centre](/docs/service-centre), [Wizard](/docs/wizard), [Commerce](/docs/commerce) and [Source](/docs/source).

[Stock](/docs/stock) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Sales | Customer quotes by status, each keeping its lines, totals and every earlier version. | Sales Engineer, Design Engineer, Service Centre, Wizard and Commerce |
| Supplier | Your suppliers' quotes, with cost, lead time and validity, never a sell price. | Source |

### Parts you meet here

- [Pricing](/docs/parts/pricing)
- [Customer context](/docs/parts/customer-context)
- [Documents](/docs/parts/documents)
- [Customer facing](/docs/parts/customer-facing)
- [Activity](/docs/parts/activity)
- [Monitoring](/docs/parts/monitoring)

### Statuses

| Status | Means |
| --- | --- |
| Draft | Being built. Most drafts come from [a request in the AI area](/docs/sales-engineer/quotes-and-orders-from-a-request); **New quote** starts one by hand. |
| Sent | Emailed with its PDF and portal link. The sent copy never changes. |
| Accepted | Accepted at the portal, or by you with **Create order**. Either way an order is raised. |
| Declined | Declined at the portal, with the customer's reason if they gave one. |
| Expired | A sent quote past its **Valid until** date. A daily pass marks it and the portal stops offering actions. |

A change that would alter what the customer received goes on a **New version**: the sent copy stays exactly as it was and is marked **Superseded**. Any other change is saved as a revision you can revert to.

### Send a quote

1. Open the quote from `/app/quotes`, in the table or the **Board view**.
2. Check the lines, the totals and **Valid until**, then choose **Send**.
3. The email goes with the PDF and the portal link, and the status moves to sent. **Resend** sends it again.

### The quote portal

The link opens `/q/<token>`: no sign in, in your brand colour. The customer sees the lines, the subtotal, any discount, the VAT and the total, and can **Download PDF**. A line priced subject to inspection says so, and requirements noted on a line are printed under it.

- **Accept quotation**, then **Confirm acceptance**, with an optional PO reference and PO file. The quote is marked accepted, an order is raised and whoever raised the quote is told.
- **Decline**, then **Confirm decline**, with an optional reason for you.
- An expired or decided quote shows no actions, and the link is rate limited.

Two automations in [Settings then Integrations](/docs/areas/settings#integrations) act on sent quotes: **Warn before a quote expires** and **Follow up on a quote nobody has answered**. Each runs only once you switch it on.

## Orders

URL: https://kabaido.ai/docs/areas/orders

Raise an order from a won quote, move it through its statuses and switch between the views your products add.

Why: Once a quote is won, the order, the purchase, the job and the delivery often live in separate systems.
What: One Orders area for every direction of work, with a view for each product that adds one.
How: Accepting a quote raises the order at its quoted prices, and any later price change needs a reason.

Find it at `/app/orders`: an area in the menu under Sales. Brought by [Sales Engineer](/docs/sales-engineer), [Design Engineer](/docs/design-engineer), [Service Centre](/docs/service-centre), [Wizard](/docs/wizard), [Commerce](/docs/commerce), [Route](/docs/route), [Source](/docs/source) and [Machinist](/docs/machinist).

[Stock](/docs/stock) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Sales | Customer orders by status, from a won quote, a purchase order or by hand. | Sales Engineer, Design Engineer, Service Centre, Wizard and Commerce |
| Purchase | Purchase orders to suppliers, with buy prices shown only to roles that see cost. | Source |
| Production | Appears with Machinist; production orders themselves sit in each machine module's Orders view. | Machinist |
| Deliveries | The same orders by fulfilment: ready, packed, dispatched, delivered and what is still owed. | Route |

### Parts you meet here

- [Pricing](/docs/parts/pricing)
- [Costing](/docs/parts/costing)
- [Traceability](/docs/parts/traceability)
- [Documents](/docs/parts/documents)
- [Customer facing](/docs/parts/customer-facing)
- [Activity](/docs/parts/activity)
- [Monitoring](/docs/parts/monitoring)

The view chips at the top show only the views your products add; with one view there are no chips.

### How an order starts

- The customer accepts the quote at the portal.
- You choose **Create order** on the quote, which also marks it accepted. A quote already converted opens its order instead.
- A purchase order sent as **Order** in the AI area comes back as an order draft; **Create order** raises it. See [quotes and orders from a request](/docs/sales-engineer/quotes-and-orders-from-a-request).
- By hand, at `/app/orders/new`.

The lines are copied from the quote with the quoted prices frozen on them, and the order says how many lines differ from the quote.

### Statuses

| Status | What else happens |
| --- | --- |
| Confirmed | Its product lines are reserved against stock. |
| In progress | Set with **Mark in progress**, or by the first dispatched delivery with Route on. |
| Fulfilled | Set with **Mark fulfilled**, or when every line is delivered with Route on. The reserved stock is issued and service items on its lines are marked returned. |
| Cancelled | Reservations are released; reopening the order takes them again. |

Edits save as a revision you can revert to, with an optional note. Once the invoice recorded on it is issued, a price change asks you to confirm the credit note or second invoice it needs. **Email** sends the branded order confirmation PDF.

### The other views

- **Purchase** (Source): purchase orders to suppliers, listed only for roles that see cost.
- **Deliveries** (Route): the same orders by fulfilment, from **Pending** through **Dispatched** to **Delivered**, with the promised date, the consignment, tracking and what is still owed.

## Customers

URL: https://kabaido.ai/docs/areas/customers

Keep one record per customer with its contacts, terms, special prices, context for the AI and, with Commerce, its sign in.

Why: Terms, contacts and order history sit in separate systems, so every reply starts with a search.
What: One record per customer: contacts, terms, addresses, special prices, quotes, orders and service items.
How: Import a CSV, add the fields your trade needs and ask the AI about any customer.

Find it at `/app/customers`: an area in the menu under Sales. Brought by every workspace.

[Inspect](/docs/inspect) and [Commerce](/docs/commerce) add to it when they are on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Customers | Search or import customers; each holds terms, prices, history and what the AI reads. | Every workspace |
| Contacts | Every person at every customer in one searchable list, linked to their record. | Every workspace |

### Parts you meet here

- [Customer context](/docs/parts/customer-context)
- [Pricing](/docs/parts/pricing)
- [Customer facing](/docs/parts/customer-facing)
- [Activity](/docs/parts/activity)
- [Monitoring](/docs/parts/monitoring)

### Add customers

1. Open `/app/customers` and choose **New customer**, or **Import CSV** for a whole book.
2. An import previews the rows and flags possible duplicates before anything is created.

### One customer's record

| Part of the record | What it holds |
| --- | --- |
| Contacts and addresses | The primary contact is the default quote recipient. Billing and shipping addresses, terms and VAT. |
| Your own fields | The fields your trade needs, defined in [Settings then Organisation](/docs/areas/settings#organisation) under **Customer fields**. |
| **Special pricing** | Prices agreed with this customer, fixed or a percentage off, by scope and date. See [special prices and customer discounts](/docs/pricing/special-prices-and-brackets). |
| Context | **Ask about this customer** opens the AI area with the customer pinned, so the answer reads their quotes, orders and items. |
| **Access** | With Commerce on: the access code, the invite link and the people signed in, with **Create access code**, **Rotate** and **Revoke**. |

The **Activity** tab lists the customer's quotes and orders and **Service items** what they have registered; a **Servicing** tab appears with Service Centre.

## Suppliers

URL: https://kabaido.ai/docs/areas/suppliers

Keep your suppliers, their contacts, their price lists and your requests for quotation in one area.

Why: Buying well needs every supplier's terms and prices in one place, next to what you sell.
What: Suppliers, their contacts, their price lists and the requests for quotation sent to them.
How: Price lists import and match to your products; requests go out and answers come back comparable.

Find it at `/app/suppliers`: an area in the menu under Sales. Brought by [Source](/docs/source).

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Suppliers | Each supplier's approval, terms, lead time, freight model and duty, beside your customers. | Source |
| Contacts | The people at each supplier, with the primary contact marked for requests. | Source |
| Price lists | Imported price lists, matched row by row to your products and activated once checked. | Source |
| RFQs | Requests for quotation sent to several suppliers, answers compared on price and landed cost. | Source |

### Parts you meet here

- [Pricing](/docs/parts/pricing)
- [Documents](/docs/parts/documents)
- [Integrations](/docs/parts/integrations)
- [Monitoring](/docs/parts/monitoring)
- [Activity](/docs/parts/activity)

### The work people do most

1. Open `/app/suppliers` and choose **New supplier** or **Import suppliers**.
2. In **Price lists**, choose **Import CSV**. Rows with no matching product wait as **Unmatched**; **Activate** makes the list the best price on offer.
3. In **RFQs**, choose **New request** and compare the answers as they arrive.

> Switch Source off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Catalogue

URL: https://kabaido.ai/docs/areas/catalogue

Find where products, schemas, imports and pricing rules live, and which products bring each view.

Why: Product data lives in supplier files and spreadsheets, so matching a request means reading them by hand.
What: One catalogue of products described by schemas, filtered by their attributes and priced by rules.
How: Import CSV, XLSX or REST feeds, map them to a schema and the AI matches requests against them.

Find it at `/app/catalog`: an area in the menu under Products. Brought by [Sales Engineer](/docs/sales-engineer), [Wizard](/docs/wizard), [Commerce](/docs/commerce), [Source](/docs/source) and [Stock](/docs/stock).

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Products | Search the grid and filter by any attribute the schema marks as a filter. | Sales Engineer, Wizard, Commerce, Source and Stock |
| Schemas | Start from a preset schema, read one from a file or build your own. | Sales Engineer, Wizard, Commerce, Source and Stock |
| Imports | Map columns, check the rows, import; REST feeds refresh nightly or on demand. | Sales Engineer, Wizard, Commerce, Source and Stock |
| Pricing | Quantity breaks by product, category, schema or service, on every quote line. | Sales Engineer, Wizard, Commerce and Source |
| Suppliers' prices | Every supplier's price for a product side by side, the best picked out. | Source |

### Parts you meet here

- [Pricing](/docs/parts/pricing)
- [Costing](/docs/parts/costing)
- [Integrations](/docs/parts/integrations)
- [Documents](/docs/parts/documents)
- [Activity](/docs/parts/activity)

Screenshot of /app/catalog?tab=schemas: The Catalogue area on its Schemas view: the product schemas the presets installed, each with its fields and facets, and no products yet.

### Build a catalogue

1. In **Schemas**, start from a preset schema or build one: it decides the fields and the filters.
2. In **Imports**, map a CSV or XLSX file to the schema and check the rows, or keep a REST feed in sync under **Connections**. See [importing products](/docs/catalog/importing-products) and [REST connections](/docs/catalog/rest-connections).
3. In **Pricing**, set the [quantity rules](/docs/pricing/quantity-rules) and [special prices](/docs/pricing/special-prices-and-brackets) every quote line reads. The old `/app/pricing` address opens this view.

## Stock

URL: https://kabaido.ai/docs/areas/stock

Read a balance per item per location, the ledger behind it and the lines under their reorder point.

Why: Promises made at the quote need a quantity that is true wherever the stock sits.
What: Stock lines, locations, the movement ledger and the reorder list, in one area.
How: Every product writes movements through one writer, and each balance is summed from them.

Find it at `/app/stock`: an area in the menu under Products. Brought by [Stock](/docs/stock).

[Design Engineer](/docs/design-engineer), [Service Centre](/docs/service-centre), [Machinist](/docs/machinist), [Route](/docs/route) and [Source](/docs/source) add to it when they are on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Lines | One balance per item per location, derived from the ledger and never typed over. | Stock |
| Locations | Every place stock is held, each renamed or counted from its own row. | Stock |
| Movements | The ledger, newest first: every receipt, issue, transfer and count, with who and when. | Stock |
| Reorder | Lines under their reorder point, turned into a supplier request or a purchase order. | Stock |

### Parts you meet here

- [Monitoring](/docs/parts/monitoring)
- [Traceability](/docs/parts/traceability)
- [Costing](/docs/parts/costing)
- [Activity](/docs/parts/activity)
- [Integrations](/docs/parts/integrations)

### Movement kinds

A balance is never typed over: it is the sum of its movements. The ledger records Opening, Receipt, Reservation, Release, Issue, Consumption, Transfer, Adjustment, Return and Write off, each with who made it and when.

Orders reserve and issue against it, and design modules, machine modules, Route deliveries and Source goods in write their own movements here. See [the ledger](/docs/stock/movements-and-the-ledger).

> Switch Stock off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Servicing

URL: https://kabaido.ai/docs/areas/servicing

Follow every customer item from registration to return, and find the service models, rules and costing behind it.

Why: A service workshop needs one place for every item, its station, its rules and its cost.
What: Servicing holds the day's work, every registered item, the service models, the rules and the costing.
How: Every view reads the same items and scans, so the registry, the rules and the costs agree.

Find it at `/app/servicing`: an area in the menu under Products. Brought by [Service Centre](/docs/service-centre).

[Commerce](/docs/commerce) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Work | Today's work, where every item is, jobs in progress and stations stacking up. | Service Centre |
| Registry | Every customer item by serial, with its customer, status, last event and times serviced. | Service Centre |
| Services | Each service model: its workflow type, steps, price formula and standard minutes. | Service Centre |
| Rules | Every workshop rule in one place: what it asks, charges or defaults. | Service Centre |
| Costing | Labour and machine rates and standard minutes in, cost and margin reports out. | Service Centre |

### Parts you meet here

- [Traceability](/docs/parts/traceability)
- [Pricing](/docs/parts/pricing)
- [Costing](/docs/parts/costing)
- [Documents](/docs/parts/documents)
- [Customer facing](/docs/parts/customer-facing)
- [Activity](/docs/parts/activity)
- [Monitoring](/docs/parts/monitoring)
- [Presets](/docs/parts/presets)

### An item's statuses

Registered, Intake, Inspection, Awaiting approval, In service, Completed, then Returned; Rejected where the work does not go ahead. See [the registry and item lifecycle](/docs/service-centre/the-registry-and-item-lifecycle).

A bench signed in with its device key works at `/app/servicing/station`. Each service model opens at `/app/servicing/services/<id>`.

> Switch Service Centre off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Design

URL: https://kabaido.ai/docs/areas/design

Open the design workbench, move between its views and find each design module's rates and stock.

Why: Made to order parts are quoted from drawings by hand, one enquiry at a time.
What: One workbench where a design module turns parameters into a model, a drawing and a price.
How: Set the parameters; the engine checks them, redraws the part and prices it from your own rates.

Find it at `/app/design`: a full screen workbench under Products. Brought by [Design Engineer](/docs/design-engineer).

[Commerce](/docs/commerce) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Parameters | Each design module's inputs, checked against its own rules as you change them. | Design Engineer |
| Model | The part in 3D, redrawn from the same parameters every time one changes. | Design Engineer |
| Files | Save, rename and duplicate designs, and pick any of them up later. | Design Engineer |
| Rates and stock | Set the rates each price line reads and match designs to stock you hold. | Design Engineer |

### Parts you meet here

- [Costing](/docs/parts/costing)
- [Pricing](/docs/parts/pricing)
- [Documents](/docs/parts/documents)
- [Customer facing](/docs/parts/customer-facing)
- [Presets](/docs/parts/presets)

`/app/design` opens where the work is: the file you had open, else your newest, else a fresh file. Each design module opens at `/app/design/<design-module>`, and its **Rates and stock** at `/app/design/<design-module>/settings`.

Design modules are installed by presets in [Settings then Presets](/docs/areas/settings#presets). With none installed, the area says so and how to add one.

> Switch Design Engineer off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Wizard

URL: https://kabaido.ai/docs/areas/wizard

Run a wizard, read its specification and see where it is embedded.

Why: Choosing the right blade or coating takes charts most buyers never see.
What: One workbench per wizard: run it, read the specification, see where it runs.
How: Each wizard installs with a preset and answers from its own sourced charts, with no model call.

Find it at `/app/wizard`: a full screen workbench under Products. Brought by [Wizard](/docs/wizard).

[Commerce](/docs/commerce) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Run | The stepped form asks what the user knows; a skipped step states its default. | Wizard |
| Results | The specification, every line naming the published chart it came from. | Wizard |
| Embed | Every run recorded in Activity and counted in Usage, with where it came from. | Wizard |

### Parts you meet here

- [Integrations](/docs/parts/integrations)
- [Customer facing](/docs/parts/customer-facing)
- [Presets](/docs/parts/presets)
- [Activity](/docs/parts/activity)

`/app/wizard` opens the wizard your workspace last ran, else the first you have, and each wizard opens at `/app/wizard/<wizard>`. A wizard answers from its own sourced charts, with no AI call per run.

> Switch Wizard off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Machinist

URL: https://kabaido.ai/docs/areas/machinist

Find each machine module's screens and the machines, operators, schedule and costs that span them.

Why: A machine shop needs its machines, people, schedule and job costs in one place.
What: The Machinist area holds each machine module's screens, plus machines, operators, schedule and costs across them.
How: Each machine module brings its own screens; machines, operators, schedule and costs span every one of them.

Find it at `/app/machinist`: a full screen workbench under Operations. Brought by [Machinist](/docs/machinist).

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Shop | Now, per machine module: open orders, the queue, low stock and the trail. | Machinist |
| Parts | Each machine module's part library, with the material every part is made from. | Machinist |
| Orders | Production orders by customer and due date: what is nested, cut or outstanding. | Machinist |
| Cut or run | The queue grouped by material and thickness, then nested onto real sheets and run. | Machinist |
| Setup | The machines, stock and cutting data each machine module reads, set once. | Machinist |
| Machines | Every machine as a station, with its hourly rate, current job and measured utilisation. | Machinist |
| Operators | Who runs which machine, their certifications and their hourly rate on the cost card. | Machinist |
| Schedule | Jobs placed on machines against the daily capacity each machine has set. | Machinist |
| Costs | What each job cost in machine time, labour and material; gaps stated, never zeroed. | Machinist |

### Parts you meet here

- [Costing](/docs/parts/costing)
- [Traceability](/docs/parts/traceability)
- [Monitoring](/docs/parts/monitoring)
- [Roles](/docs/parts/roles)
- [Presets](/docs/parts/presets)
- [Activity](/docs/parts/activity)

### Where each screen lives

| Screen | Route |
| --- | --- |
| One machine module's Shop, Parts, Orders, Setup and its **Nest and cut**, **Erode** or **Run** view | `/app/machinist/<machine-module>` and below |
| Machines, Operators, Schedule and Costs | `/app/machinist/machines`, `/operators`, `/schedule`, `/costs` |
| The planner: jobs, processes and consumables | `/app/machinist/planner` |
| A machine station | `/app/machinist/station` |

> Switch Machinist off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Route

URL: https://kabaido.ai/docs/areas/route

Take a confirmed order to the door: deliveries, runs, loading, vehicles and couriers.

Why: A promised delivery date is only useful if the day, the van and the proof all hold.
What: The consignments, runs, loading, vehicles and couriers that take a confirmed order to the door.
How: Deliveries come from orders, runs sequence the stops and every scan writes a trace event.

Find it at `/app/route`: a full screen workbench under Operations. Brought by [Route](/docs/route).

[Commerce](/docs/commerce) adds to it when it is on as well.

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Deliveries | Every consignment with its promised window, packages, state, tracking and delivery cost. | Route |
| Runs | One vehicle's day of stops, sequenced, with straight line distance and arrival times. | Route |
| Loading | Scan each package aboard, last drop first; the missing count stays until zero. | Route |
| Vehicles | Vans with capacity, rates, MOT and service dates, and days off the road. | Route |
| Couriers | Carrier accounts, what each carries and costs, and tracking links where you set one. | Route |

### Parts you meet here

- [Traceability](/docs/parts/traceability)
- [Monitoring](/docs/parts/monitoring)
- [Documents](/docs/parts/documents)
- [Customer facing](/docs/parts/customer-facing)
- [Costing](/docs/parts/costing)
- [Activity](/docs/parts/activity)

### A delivery's states

Pending, Ready, Picked, Packed, Dispatched, Out for delivery, then Delivered; Failed where it does not arrive, and Returned when delivered goods come back. See [the delivery lifecycle](/docs/route/the-delivery-lifecycle). The order side of this is the **Deliveries** view in [Orders](/docs/areas/orders).

**Runs**, **Loading** and **Vehicles** open only when the workspace's own transport setting is on; until then Route works through **Deliveries** and **Couriers**. There is no switch for it in Settings yet; see [vans and runs](/docs/route/vans-and-runs). A driver's van signs in and works at `/app/route/drive`.

> Switch Route off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Inspect

URL: https://kabaido.ai/docs/areas/inspect

Move around the Inspect workbench: the region, your lists, the planner, companies, campaigns, your offering and one company's profile.

Why: Territory knowledge lives in a few heads, so the best prospects wait for the right person.
What: Seven views over one region: the map, lists, a visit run, companies, campaigns, your offering, profiles.
How: Every view reads the same evidenced profiles, ranked against your offering map and sharpened by debriefs.

Find it at `/app/inspect`: a full screen workbench under Growth. Brought by [Inspect](/docs/inspect).

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Region | The county as a list or a map, every verified company in it: the front door. | Inspect |
| Lists | Saved lists of the companies you choose to work next. | Inspect |
| Planner | Every company being worked, by day and postcode district, with its visit agenda. | Inspect |
| Companies | Every company you are working, with its status, owner and next action. | Inspect |
| Campaigns | Email sequences to the contacts you hold, from your own inbox. | Inspect |
| Offering | Your offering map, loaded once, which ranks what to lead with. | Inspect |
| Company | One company's evidenced profile, commercial panel, contacts and visit preparation. | Inspect |

### Parts you meet here

- [Customer context](/docs/parts/customer-context)
- [Integrations](/docs/parts/integrations)
- [Activity](/docs/parts/activity)
- [Monitoring](/docs/parts/monitoring)

`/app/inspect` opens on the **Region** view. Each company's profile opens at `/app/inspect/company/<id>` and each campaign at `/app/inspect/campaigns/<id>`.

> Switch Inspect off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Commerce

URL: https://kabaido.ai/docs/areas/commerce

See who uses your customer sign in, and run your trade website once one is connected.

Why: The answers your customers ring for already sit in your workspace.
What: Customers online shows your sign in and who uses it; Website runs the trade site once one is connected.
How: An access code per customer record, your own address or domain and site orders landing as platform orders.

Find it at `/app/commerce`: a full screen workbench under Growth. Brought by [Commerce](/docs/commerce).

### Views

| View | What it shows | Added by |
| --- | --- | --- |
| Customers online | Your addresses, invited customers and their codes, live sessions, activity and the AI switch. | Commerce |
| Website | Overview, content, enquiries, blog and checklists for a connected site; otherwise the build offer. | Commerce |

### Parts you meet here

- [Customer facing](/docs/parts/customer-facing)
- [Integrations](/docs/parts/integrations)
- [Documents](/docs/parts/documents)
- [Activity](/docs/parts/activity)

**Customers online** opens at `/app/commerce` and **Website** at `/app/commerce/website`. With a site connected, its Overview, Content, Enquiries, Blog and Checklists open under `/app/commerce`, such as `/app/commerce/enquiries`.

The address, the brand and what customers may use are set in [Settings then Customer facing](/docs/areas/settings#customer-facing).

> Switch Commerce off and, while this area still holds records, it stays readable under a banner that says so. Nothing is deleted, and changes are refused until it is back on in [Settings then Products](/docs/areas/settings#products).

## Settings

URL: https://kabaido.ai/docs/areas/settings

Know what each settings section holds and who can open it.

Why: Workspace setup belongs in one place, not scattered across the areas it affects.
What: The sections from your own profile to the plan, each behind the role it needs.
How: Open `/app/settings`; the sections your role reaches are listed down the side.

Find it at `/app/settings`: opened from the account menu at the foot of the menu. Brought by every workspace.

### Parts you meet here

- [Roles](/docs/parts/roles)
- [Presets](/docs/parts/presets)
- [Integrations](/docs/parts/integrations)
- [Activity](/docs/parts/activity)
- [Customer facing](/docs/parts/customer-facing)

### Profile

`/app/settings/profile`, any member: your name, photo, email, appearance and password, and replaying the tour.

### Users and roles

`/app/settings/users`, admin: invite people by **Role templates**, which set the role, the areas and the stations in one go, then change any member's access. See [users, roles and stations](/docs/getting-started/users-roles-and-permissions).

### Organisation

`/app/settings/organisation`, admin: **Company** details and the platform version, with the **Source** block when Source is on (who may send a purchase order, over receipt, invoice tolerance, price alerts and **Accepted exchange rates**), **Templates** for document numbering and terms, **Customer fields**, **Stations** with their device keys and **What the AI has learned**.

### Products

`/app/settings/products`, admin: switch each product on or off, with what it brings and what switching it off does. Every product is on every plan. See [how your workspace adapts](/docs/platform/how-your-workspace-adapts).

### Presets

`/app/settings/presets`, any member to read and an admin to install a trade's product schemas, design modules, wizards, machine modules, service models and customer fields. See [presets](/docs/parts/presets).

### Integrations

`/app/settings/integrations`, admin: connections, the email agent, API keys, MCP, webhooks, inbound endpoints and automations. See [connecting other systems](/docs/integrations/connecting-other-systems).

### Notifications

`/app/settings/notifications`, admin: **To your team**, **To your customers** and **Monitors**, each email set to off, straight away or the daily digest.

### Customer facing

`/app/settings/customer-facing`, admin, with Commerce on: the address customers sign in at, your own domain, your brand, what they may use, the customer AI switch and the welcome. See [customer facing settings](/docs/commerce/customer-facing-settings).

### Billing

`/app/settings/billing`, the owner; admins, and a member whose access includes Billing, read it only: the plan, the usage bar, the daily budget and invoices. See [plans and usage](/docs/billing/plans-and-usage).

## Scan station

URL: https://kabaido.ai/docs/areas/scan-station

Scan a code at a bench or a dock, record what happened to it and sign a device in with its key.

Why: Work moves fastest when a scan records it where it happens, without a desk in between.
What: One full screen at `/app/scan`: scan or type a code, see what it is and record the next event.
How: A member of operator rank or above opens it from the platform; a device signs in at `/station` with its own key.

Find it at `/app/scan`: a station screen. Brought by [Service Centre](/docs/service-centre), [Stock](/docs/stock), [Route](/docs/route) and [Machinist](/docs/machinist).

### Parts you meet here

- [Traceability](/docs/parts/traceability)

### Scan a code

1. At `/app/scan`, scan or type the code and choose **Resolve**, or **Use the camera**.
2. The screen shows what the code is and its **Last event**. Pick the next event and choose **Record**.
3. A code it does not know offers **Register this code** or **Add as an alias of the next code**.

Without signal, trace scans queue on the device and send when it returns. With Stock on, the screen adds a **Stock** panel ([scanning stock](/docs/stock/scanning-stock)); with Source on, **Receive** for [goods in](/docs/source/goods-in). Stock moves and receipts need a connection.

### Sign a device in

1. An admin opens [Settings then Organisation](/docs/areas/settings#organisation), **Stations**, and chooses **Add station**. The key is shown once: copy it.
2. On the device, open `/station`, enter the **Device key** and choose **Sign in**.

A station signs in, not a person, and reaches one screen by its kind: `/app/scan`, `/app/servicing/station`, `/app/machinist/station` or `/app/route/drive`. **Rotate key** signs the old screen out; **Deactivate** stops the station and keeps its trail.

# Docs: Parts

## Pricing

URL: https://kabaido.ai/docs/parts/pricing

Know where your own prices are set and how a quote line shows the steps that reached its price.

Why: A price is only trusted when everyone can see how it was reached.
What: Discounts, special prices and quantity breaks set per customer, product, category or service, applied on every quote line.
How: A rule or a special sits against a product, category, schema, design module or service, and the most specific wins.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | A how priced popover on every quote line, with its margin | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Orders](/docs/areas/orders) | Each order line held against the price it was quoted | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Customers](/docs/areas/customers) | Special prices on the customer record, dated, with a worked example | Every workspace |
| [Suppliers](/docs/areas/suppliers) | Supplier price lists, accepted as cost and never as a sell price | Source |
| [Catalogue](/docs/areas/catalogue) | Quantity breaks and special prices in the catalogue's Pricing view | Sales Engineer, Wizard, Commerce, Source and Stock |
| [Servicing](/docs/areas/servicing) | Each service model priced from its own definition | Service Centre |
| [Design](/docs/areas/design) | A price panel with its working beside every design | Design Engineer |

### The detail lives in Pricing and costing

Pricing is one dataset read by every area that shows a price. How it works, step by step, is in the [Pricing and costing](/docs/pricing) group:

- [Pricing rules and the resolution order](/docs/pricing/pricing-rules-and-the-resolution-order): which price wins, and why.
- [Special prices and customer discounts](/docs/pricing/special-prices-and-brackets): an agreed price or discount for one customer.
- [Quantity rules](/docs/pricing/quantity-rules): a unit price that falls as the quantity rises.
- [Margins at scale](/docs/pricing/margins-at-scale): move prices and costs across many products at once.

> This is how you price for your customers. The Kabaido plans themselves are on the [pricing page](/pricing).

## Costing

URL: https://kabaido.ai/docs/parts/costing

Know where the cost behind each margin comes from, and who can see it.

Why: A margin is only real when the cost behind it is measured, not assumed.
What: Costs held against products, stock, machines, operators, service steps and delivery runs, each from a real figure.
How: Work is timed where it happens and costed at your rates; a missing rate shows as a gap.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Orders](/docs/areas/orders) | Landed unit cost on goods in against a purchase order | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Catalogue](/docs/areas/catalogue) | A cost on every product, accepted from supplier prices | Sales Engineer, Wizard, Commerce, Source and Stock |
| [Stock](/docs/areas/stock) | A moving average unit cost on every stock line | Stock |
| [Servicing](/docs/areas/servicing) | Standard against actual minutes per step, with labour and machine rates | Service Centre |
| [Design](/docs/areas/design) | A cutting cost from the shop's own cut chart | Design Engineer |
| [Machinist](/docs/areas/machinist) | Job cost per machine and operator on the Costs screen | Machinist |
| [Route](/docs/areas/route) | A run's cost shared across the deliveries it carried | Route |

### Who sees cost

Costs and margins in Servicing, Machinist, Stock, Suppliers' prices and purchase orders are shown to the **engineer** role and above, and operators see neither. A quote line's margin, read from the cost copied onto the line, shows to everyone who can open the quote. See [Roles](/docs/parts/roles).

### The detail lives in Pricing and costing

- [Where cost comes from](/docs/pricing/where-cost-comes-from): supplier prices, stock, rates and measured minutes.
- [Margin reporting](/docs/pricing/margin-reporting): the margin by line, customer and month.

> A missing rate is shown as missing, never costed at zero. Set the rate and the cost appears.

## Customer context

URL: https://kabaido.ai/docs/parts/customer-context

Pin a customer to a thread so the AI answers with what you know about them, and nothing about anyone else.

Why: The right answer depends on who is asking and what they bought before.
What: Custom fields, patterns and history on every customer, fed to the AI only when you pin that customer.
How: Pinning a customer adds their counts, dates and fields, never a price or another customer's rows.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [AI](/docs/areas/ai) | Pin a customer in the composer and the answer carries their context | Every workspace |
| [Quotes](/docs/areas/quotes) | The quote's customer, one click from the quote to their record | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Customers](/docs/areas/customers) | Custom fields, quote and order activity, and an Ask AI link | Every workspace |
| [Inspect](/docs/areas/inspect) | Make a profiled company a customer in one step | Inspect |

### Pin a customer

1. Open `/app` and choose the **Customer** chip in the composer.
2. Type in **Find a customer** and pick one. The thread is now pinned to them.
3. Send the request. Clear the chip to unpin the thread.

When a request names a customer you hold, the chip suggests them (**For Customer A?**). Nothing is used until you pin the suggestion. On a customer record, **Ask about this customer** opens the AI already pinned.

### What the AI reads

| Read | Never read |
| --- | --- |
| How many orders and order lines over the last 24 months | Any other customer's rows |
| Median lead time, order cadence and typical quantities | A price, a cost, a margin or a supplier |
| Most ordered products and most used services | A contact's email or phone |
| Open quotes, overdue orders and service items due | Free text notes and internal quote notes |
| Your custom fields on the record | A field whose value holds an email, a phone or a money figure |

The figures are counted by the database, not written by the model, and the block the AI receives has a hard size cap, so pinning adds only a little to a request.

### Custom fields

Add fields in [Settings then Organisation](/docs/areas/settings#organisation) under **Customer fields**, with **New field**. A preset adds the fields its trade works with, such as a collection day.

## Monitoring

URL: https://kabaido.ai/docs/parts/monitoring

Set a monitor on an area so the team hears when a quote, order, stock line or delivery needs attention.

Why: Nobody can watch every quote, order and stock line all day.
What: Watchers set against an area that check on a schedule and act when something changes.
How: Each monitor checks every fifteen minutes, hourly or daily, then notifies the team or calls a webhook.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | Quote unanswered, quote expiring and a saved list crossing a number | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Orders](/docs/areas/orders) | Order overdue, past its promised or expected date | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Customers](/docs/areas/customers) | Customer gone quiet and customer came back | Every workspace |
| [Suppliers](/docs/areas/suppliers) | Supplier price moved past a set percentage | Source |
| [Stock](/docs/areas/stock) | Stock below a level and reorder point reached | Stock |
| [Servicing](/docs/areas/servicing) | Service due, a set number of days ahead | Service Centre |
| [Machinist](/docs/areas/machinist) | Machine idle, with no run recorded for a set time | Machinist |
| [Route](/docs/areas/route) | Delivery late, minutes past the close of its window | Route |
| [Inspect](/docs/areas/inspect) | A new signal on a company you are tracking | Inspect |

### Add a monitor

1. Open the area, for example `/app/quotes` or `/app/stock`, and choose **Monitors**.
2. Under **Add a monitor**, pick a kind and fill in its fields.
3. Choose **Add it**. The sheet then shows when it last checked and last fired.

### The kinds

| Monitor | Area | Needs | Checks | Who can add it |
| --- | --- | --- | --- | --- |
| Stock below a level | Stock | Stock | Every hour | engineer and above |
| Reorder point reached | Stock | Stock | Once a day | engineer and above |
| Customer gone quiet | Customers | Every workspace | Once a day | sales and above |
| Customer came back | Customers | Every workspace | Once a day | sales and above |
| Quote unanswered | Quotes | Every workspace | Once a day | sales and above |
| Quote expiring | Quotes | Every workspace | Once a day | sales and above |
| Order overdue | Orders | Every workspace | Once a day | sales and above |
| Delivery late | Route | Route | Every fifteen minutes | engineer and above |
| Service due | Servicing | Service Centre | Once a day | engineer and above |
| Machine idle | Machinist | Machinist | Every hour | engineer and above |
| Supplier price moved | Suppliers | Source | Every hour | engineer and above |
| Signal on a tracked company | Inspect | Inspect | Once a day | sales and above |
| A saved list crosses a number | Quotes | Every workspace | Once a day | sales and above |

A monitor added from the sheet notifies your team: a fired monitor lands in the bell. The switch on each row turns it off and on.

> Each monitor has a daily limit: past it, the day's further hits are recorded without acting, and one notification says the limit was reached. A monitor whose product is switched off is paused, never deleted.

## Traceability

URL: https://kabaido.ai/docs/parts/traceability

Read a Kabaido code, follow its trail and choose what a public scan of your label shows.

Why: When a customer asks where their item is, the answer should take one scan.
What: One Kabaido code on any item, batch, package or job, scanned and followed through the platform and the workshop.
How: Each scan writes an event with its station and the minutes since the last scan onto the trail.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Orders](/docs/areas/orders) | A lot code on every goods in receipt line | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Stock](/docs/areas/stock) | Every movement an append only ledger row, with a trace event | Stock |
| [Servicing](/docs/areas/servicing) | One code for an item's life, the customer's asset number as alias | Service Centre |
| [Machinist](/docs/areas/machinist) | A code per shop job, with station in and out events | Machinist |
| [Route](/docs/areas/route) | A code on every delivery and package, signature on the event | Route |

### Reading a code

A code reads `ABC-P26-00148`: your workspace's serial prefix, a type letter, the two digit year and a sequence. An item keeps the serial it was registered with, such as `ABC-26-00147`: it carries no letter and is read as an item.

| Letter | Traces |
| --- | --- |
| `I` | item (reserved: an item keeps its serial, with no letter) |
| `B` | batch |
| `P` | package |
| `J` | job |
| `D` | delivery |
| `L` | lot |
| `O` | order line |

Every label carries the code twice: a QR that opens `/t/<code>` and a Code 128 line for a scanner. A customer's asset number or a courier's tracking number is kept as an alias, so either finds the same trail.

### What a public scan shows

Anyone who scans a label without signing in lands on `/t/<code>`, rate limited per address. Set how much it says in [Settings then Customer facing](/docs/areas/settings#customer-facing), under **What a public scan shows**:

| Setting | Shows |
| --- | --- |
| **Says nothing** (the default) | Only that the code belongs to a Kabaido workspace, with a sign in link |
| **The item and where it is** | What the item is, its status and when it is due back |
| **The item, where it is and what has happened** | The above and the dates it moved, with no names and no places |

> A public scan never shows a customer, a price or who did the work. A signed in member or customer is sent to the full record instead.

## Integrations

URL: https://kabaido.ai/docs/parts/integrations

Find where each kind of connection is documented, from a CSV import to the REST API and MCP.

Why: The platform has to fit the systems a business already runs, not replace them overnight.
What: Connections tailored per product, custom REST connections, signed webhooks, a REST API and an MCP server.
How: An admin connects each one in Settings, and API keys scope every call to one organisation.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [AI](/docs/areas/ai) | Connected email inboxes in the composer's Integrations menu | Every workspace |
| [Suppliers](/docs/areas/suppliers) | Price list imports and RFQs by email to any supplier | Source |
| [Catalogue](/docs/areas/catalogue) | CSV imports, a daily REST sync and the API's bulk upsert | Sales Engineer, Wizard, Commerce, Source and Stock |
| [Stock](/docs/areas/stock) | Stock lines, locations and movements over the REST API | Stock |
| [Wizard](/docs/areas/wizard) | A wizard embedded on your own website with its own embed key | Wizard |
| [Inspect](/docs/areas/inspect) | Contact finders on your own key and your own account | Inspect |
| [Commerce](/docs/areas/commerce) | Your website's enquiries and activity sent in on a site key | Commerce |

### Every plan can connect

Integrations are not a plan feature: the free plan can connect the same systems as any other. An admin connects them in [Settings then Integrations](/docs/areas/settings#integrations). Ultra and Max also include hands on help wiring connectors up and keeping them running.

### Where to read on

| You want to | Read |
| --- | --- |
| See every provider and its status | [Connecting other systems](/docs/integrations/connecting-other-systems), or [Integrations](/integrations) on the website |
| Import or export a file | [CSV import and export reference](/docs/integrations/csv-import-export-reference) |
| Keep a catalogue in sync from another system | [REST connections](/docs/catalog/rest-connections) |
| Call Kabaido from your own code | [API keys and scopes](/docs/api/api-keys-and-scopes) and [the REST API](/docs/api/the-rest-api) |
| Hear about changes in your system | [Webhooks](/docs/api/webhooks) |
| Post a status in from your ERP | [Inbound endpoints](/docs/api/inbound-endpoints) |
| Work with an AI assistant of your own | [MCP](/docs/api/mcp) |
| Answer requests from your own inbox | [The email agent](/docs/sales-engineer/the-email-agent) |

## Roles

URL: https://kabaido.ai/docs/parts/roles

Give a person the right role, areas and stations in one pick, and know what each role can change.

Why: People should see the work they do, and a station should never show a price.
What: Five ranked roles plus operator, and job templates that set a person's role, areas and stations in one pick.
How: The ranked role decides what the database lets them change; the areas only narrow what their menu shows.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Machinist](/docs/areas/machinist) | The operator role and a machine station signed in by device key | Machinist |

### The roles

| Role | Can |
| --- | --- |
| owner | Everything an admin can, plus billing and the plan |
| admin | Settings, members, pricing rules, integrations, API keys and imports |
| engineer | The catalogue, schemas, design modules, servicing and stock; sees costs |
| sales | Creates and edits requests, quotes, orders and customers |
| operator | Works at stations and moves jobs; never sees a price, a cost or a margin |
| viewer | Reads, and changes nothing |

The role decides what someone can change. Their **areas** only narrow what their menu shows.

### Invite by job

1. Open `/app/settings/users`, enter their email under **Invite a teammate** and pick a **Role template**.
2. Choose **Customise** to change the areas or stations, then **Invite**.
3. Later, **Access** on a member edits them, and **Save as a template** keeps that setup for the next person.

A template only fills in the invite. Nothing reads it afterwards, so removing one takes nothing from anybody. Each template is offered only when a product it is for is on.

| Template | Role | Areas | Stations |
| --- | --- | --- | --- |
| Internal Sales | sales | AI, Quotes, Orders and Customers | None |
| Applications Engineer | engineer | AI, Quotes, Orders, Customers, Catalogue, Design, Wizard and Servicing | None |
| Estimator | sales | Quotes and Catalogue | None |
| Buyer | engineer | Suppliers, Orders and Stock | None |
| Stores | engineer | Stock, Orders and Scan | Scan |
| Service Manager | engineer | Servicing, Orders and Customers | None |
| Bench Operator | operator | Servicing | Bench |
| Production Manager | engineer | Machinist, Orders and Stock | None |
| Operator | operator | Machinist and Scan | Machine and Scan |
| Transport Manager | engineer | Route and Orders | None |
| Driver | operator | Their stations only | Driver |
| Field Sales | sales | Inspect, Customers and Route | None |
| Marketing | sales | Inspect, Commerce and Wizard | None |
| Finance | viewer | Orders, Customers, Suppliers and Billing (read) | None |
| Administrator | admin | Every area | None |

### Stations

An admin creates stations and issues their device keys in [Settings then Organisation](/docs/areas/settings#organisation), under **Stations**. A member who holds a station opens it from **Stations** in the menu and works it under their own name. A shared screen nobody is signed in to uses its device key at `/station`.

## Presets

URL: https://kabaido.ai/docs/parts/presets

Set a workspace up for your trade in one step, at onboarding or later, and know what a preset will and will not touch.

Why: A new workspace should start knowing the trade, not as a blank form.
What: Ready made setup for a trade, applied at onboarding or later, with schemas, design modules, wizards and service models.
How: Installing adds what the preset carries and asks before switching a product on; it creates no sample products.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Servicing](/docs/areas/servicing) | A service model installs its families, workflows and rules, switched off | Service Centre |
| [Design](/docs/areas/design) | Design modules added, and kept while a saved design uses them | Design Engineer |
| [Wizard](/docs/areas/wizard) | The installed presets decide which wizards the area offers | Wizard |
| [Machinist](/docs/areas/machinist) | Machine interfaces on, and an inactive station per machine | Machinist |

Screenshot of /app/settings/presets: Settings then Presets: the presets grouped by trade, with what each sets up as small counts and the ones turned on marked On.

A preset answers one question: what do you sell, and what do you service. Several can be on at once; [Presets by trade](/docs/parts/presets-by-trade) lists what each one sets up.

### Turn one on

At onboarding, the last screen asks **What do you sell or service?** and offers the presets your chosen products carry. No sample products, customers or prices are ever created. Later:

1. Open `/app/settings/presets` and search by what you sell.
2. Open a preset to see what it sets up, who it suits and what it does not cover.
3. Choose **Turn on**. If it needs a product you have off, it asks before switching that product on.
4. Read the report: every item is **Added**, **Already there** or **Not added** with the reason.

- Services and service models arrive switched off: their figures are starting points. Set your rates, then switch each one on.
- A machine arrives as an inactive station with no rate, and an inactive station cannot sign in. Add the machine under [Machines](/docs/machinist/machines-and-stations), which issues a working device key.
- Services count against your plan's allowance (2 on the free plan). A service that does not fit is listed as **Not added** with the reason, and the rest of the preset still goes in.

### Improvements reach you

When a preset you have grows, it shows **Update**: updating adds the new pieces and touches nothing you have filled in. Kabaido also runs the same additive update across existing workspaces when it improves a preset.

### Turn one off

**Turn off** takes back the offer, not your work. A schema with products stays, a service is paused with its history, a customer field is archived with its values kept, and a design module with saved designs stays on.

> A preset never changes what the AI knows: full [Application Engineering Intelligence](/docs/platform/application-engineering-intelligence) is on for every workspace. Only an admin or owner changes the set; everyone can read it.

## Presets by trade

URL: https://kabaido.ai/docs/parts/presets-by-trade

Find the preset for what you sell or service, and see exactly what it sets up before you turn it on.

Why: Most businesses need more than one preset, and each should read as something you sell.
What: Every preset in the platform, grouped by how the trade works, with what each one sets up.
How: Pick by what you do: a business that sells blades and sharpens them turns on one from Tooling and consumables and one from Service centres.

### Tooling and consumables

Ranges that are described by a specification and quoted from a catalogue.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Cutting tools | Solid and indexable metal cutting tools | Wizard: Machining tool selector; 3 product schemas | Sales Engineer and Wizard |
| Indexable tooling | Inserts, holders, grades and chipbreakers | Wizard: Machining tool selector; 1 product schema | Sales Engineer and Wizard |
| Saw blades | Bandsaw, circular, cold saw and tipped blades | Design module: PCD saw blades; Wizards: Bandsaw blade wizard and PCD saw blade selector; 4 product schemas | Sales Engineer, Design Engineer and Wizard |
| Industrial blades and knives | Machine knives, guillotine blades and profile knives | 2 product schemas | Sales Engineer |
| Grinding wheels and abrasives | Bonded, coated and superabrasive | 2 product schemas | Sales Engineer |
| PCD and diamond tooling | Brazed and tipped polycrystalline diamond | Design modules: PCD saw blades, PCD profile cutters and PCD shank tools; Machine modules: Wire EDM and CNC milling; 2 inactive stations; Wizard: PCD saw blade selector; 3 product schemas | Sales Engineer, Design Engineer, Machinist and Wizard |
| Gear cutting tools | Hobs, shaper cutters and shaving tools | 1 product schema | Sales Engineer |

### Machine shop

What runs beside the machine: workholding, spares, gauges and fluids.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Toolholding and workholding | Chucks, holders, vices and soft jaws | Design module: Soft jaws; 1 product schema | Sales Engineer and Design Engineer |
| Machines, spares and maintenance | Machine tools, spare parts and service visits | 1 service; 1 product schema; 3 customer fields | Sales Engineer and Service Centre |
| Metrology and inspection | Gauges, instruments and measuring equipment | 1 product schema | Sales Engineer |
| Fluids, coolants and lubricants | Cutting fluids, oils, greases and cleaners | 1 product schema | Sales Engineer |
| Machined parts and subcontract machining | Parts made to a customer drawing | 1 product schema; 2 customer fields | Sales Engineer |

### Made to order

Work quoted per job from sizes and a drawing rather than from a part number.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Balustrades and architectural metalwork | Guarding, handrail runs, glass and staircases | Design module: Balustrades and handrails; 2 product schemas; 3 customer fields | Sales Engineer and Design Engineer |
| Gaskets and sealing | Flange gaskets, cut shapes and sheet materials | Design module: Gaskets; 2 product schemas; 2 customer fields | Sales Engineer and Design Engineer |
| Cut-to-size plastics | Sheet, rod and tube cut to a customer size | Design module: Cut to size plastics; 1 product schema; 3 customer fields | Sales Engineer and Design Engineer |
| Plate profiling and cutting | Plasma, laser and waterjet profiling from plate | Machine module: Arcline plasma; 1 inactive station; 1 product schema; 3 customer fields | Sales Engineer and Machinist |
| Solid round tools | Endmills and form cutters ground from carbide rod to a specification | Design module: Solid carbide endmills; 1 product schema | Sales Engineer and Design Engineer |
| Solid carbide tool making | Endmills designed and ground to order | Design module: Solid carbide endmills; Machine module: Tool grinding; 2 inactive stations | Design Engineer, Stock and Machinist |
| Machine knives | Profile ground straight and circular knives made to a drawing | **Built to order**: nothing to set up yet. **Request this build** books a scoping call. | Design Engineer |
| Superabrasive wheels | Diamond and CBN wheels specified by shape, segment and bond | **Built to order**: nothing to set up yet. **Request this build** books a scoping call. | Design Engineer |
| Woodworking cutter heads | Planing and profiling heads carrying insert seats | **Built to order**: nothing to set up yet. **Request this build** books a scoping call. | Design Engineer |
| Coating racks and jigs | Racks and jigs built around the parts they carry | **Built to order**: nothing to set up yet. **Request this build** books a scoping call. | Design Engineer |

### Materials and treatment

Stock you hold and processes you put it through.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Materials and stock | Bar, plate, sheet, tube and section | 1 product schema | Sales Engineer and Stock |
| Coatings and surface treatment | PVD, CVD and applied coatings | Wizard: Coating and treatment selector; 1 service; 1 product schema; 3 customer fields | Sales Engineer, Service Centre and Wizard |

### Distribution ranges

Broad factory supply ranges, sold on availability and account terms.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Fasteners and fixings | Bolts, screws, anchors and washers | 1 product schema | Sales Engineer |
| Bearings and power transmission | Bearings, belts, chain, couplings and gearing | 1 product schema | Sales Engineer |
| Hydraulics, pneumatics and sealing | Hose, fittings, cylinders, valves and seals | 1 product schema | Sales Engineer |
| Welding consumables and gas | Wire, rod, flux, gas and welding equipment | 1 product schema | Sales Engineer |
| MRO consumables and PPE | Site consumables, safety and general supply | 1 product schema | Sales Engineer |

### Service centres

Work you do on a customer's own item and send back to them.

| Preset | Covers | Sets up | Needs |
| --- | --- | --- | --- |
| Tool regrind and recoat | Solid tools sharpened and recoated | Service model: Solid tool regrind and recoat; 3 services; 2 product schemas; 3 customer fields | Sales Engineer and Service Centre |
| Saw sharpening and retipping | Circular, band and cold saw blades serviced | Service model: Saw blade sharpening and retipping; 2 services; 3 customer fields | Service Centre |
| Blade and knife regrind | Machine knives and industrial blades reground | Service model: Blade and knife regrind; 2 services; 3 customer fields | Service Centre |
| Wheel re-profiling and balancing | Grinding wheels re-profiled to drawing | Service model: Wheel re-profiling and balancing; 2 services; 3 customer fields | Service Centre |
| PCD re-tip and regrind | Brazed PCD tools re-tipped and reground | Service model: PCD re-tip and regrind; 1 service; 3 customer fields | Service Centre |
| Hob sharpening and recoat | Gear hobs resharpened on the flutes | Service model: Hob sharpening and recoat; 1 service; 3 customer fields | Service Centre |
| Toolholder restoration and balancing | Tapers cleaned up, inspected and balanced | Service model: Toolholder taper restoration and balancing; 1 service; 3 customer fields | Service Centre |
| Calibration and certification | Gauges calibrated, material certified | Service model: Gauge and instrument calibration; 2 services; 1 product schema; 5 customer fields | Sales Engineer and Service Centre |
| Coolant management | Sumps cleaned out, refilled and monitored | Service model: Coolant system clean-out and refill; 1 service; 1 product schema; 3 customer fields | Sales Engineer and Service Centre |
| Surface treatment and metal finishing | Plating, zinc flake, e-coat and conversion coatings | Wizard: Coating and treatment selector; Service model: Batch surface treatment; 10 services; 5 customer fields | Service Centre and Wizard |

> Nothing matches what you sell? In `/app/settings/presets`, the **Nothing here matches what you sell?** card offers **Book a scoping call** for a custom build. See [Custom design modules and the roadmap](/docs/design-engineer/custom-modules-and-the-roadmap).

## Customer facing

URL: https://kabaido.ai/docs/parts/customer-facing

Know which product brings your customers' own surface, and where its guides live.

Why: Customers want to check a quote or an order without waiting for someone to reply.
What: Your own customers on a branded surface of the same platform, brought by Commerce, reading only their own rows.
How: A customer signs in with an access code, as a separate principal, never as one of your members.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | Accept a quote with a PO reference, or decline with a reason | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Orders](/docs/areas/orders) | Status, lines, totals, the invoice reference and the order's documents | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Customers](/docs/areas/customers) | An access code per customer record to invite them in | Every workspace |
| [Servicing](/docs/areas/servicing) | Their own items, each decision priced, and collection in one tap | Service Centre |
| [Design](/docs/areas/design) | Their saved designs, read only, with Ask for a quote | Design Engineer |
| [Wizard](/docs/areas/wizard) | Wizards they run themselves, charged to your organisation | Wizard |
| [Route](/docs/areas/route) | Delivery windows, tracking and proof of delivery | Route |
| [Commerce](/docs/areas/commerce) | Brings the surface: your prefix, your brand, your own domain | Commerce |

### Brought by Commerce

The signed in surface your customers use is brought by [Commerce](/docs/commerce). A customer is a separate kind of user, invited with an access code, who reads only their own rows and is never one of your members.

Quote links (`/q/...`), document links (`/doc/...`) and an embedded wizard work without Commerce.

### Read on

- [The customer surface](/docs/commerce/the-customer-surface): what your customers see, on your Kabaido address.
- [Your own domain](/docs/commerce/your-own-domain): the same surface on your domain.
- [The website build](/docs/commerce/the-website-build): a whole website built around it.

## Activity

URL: https://kabaido.ai/docs/parts/activity

Read what happened in the workspace and choose who hears about each kind of event, in the app and by email.

Why: The team should hear about the moments that matter without watching every screen.
What: Every action recorded, and the notifications your team and your customers receive, each tuned per kind.
How: Each kind has a setting for the app and for email, which you or each person can change.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [AI](/docs/areas/ai) | A new request from a connected inbox, in the bell | Every workspace |
| [Quotes](/docs/areas/quotes) | Sent, opened and accepted, each a notification | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Orders](/docs/areas/orders) | Every status move on the order's trail, with its reason | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Customers](/docs/areas/customers) | An Activity tab of the customer's quotes and orders | Every workspace |
| [Suppliers](/docs/areas/suppliers) | A price moved notification when a list activates | Source |
| [Catalogue](/docs/areas/catalogue) | Import finished or failed, in the bell | Sales Engineer, Wizard, Commerce, Source and Stock |
| [Stock](/docs/areas/stock) | Counts, locations and movements recorded to the activity stream | Stock |
| [Servicing](/docs/areas/servicing) | Each move a service event and a trace event, together | Service Centre |
| [Wizard](/docs/areas/wizard) | No match and website run notifications | Wizard |
| [Machinist](/docs/areas/machinist) | Nest cut and stock low notifications from the plasma shop | Machinist |
| [Route](/docs/areas/route) | Delivery completed recorded with the signature, and a webhook | Route |
| [Inspect](/docs/areas/inspect) | A new signal on a tracked company, in the bell | Inspect |
| [Commerce](/docs/areas/commerce) | Your website's activity, in the bell | Commerce |

### The bell and the Activity page

The bell on every screen holds your notifications. Open `/app/activity` for the full list, ranked by what needs a decision first:

| View | Shows |
| --- | --- |
| **Notifications** | Your notifications, by priority or newest first, filtered by area |
| **Team** | Who opened which screens and what they did; admins and owners only |
| **Setup** | The setup steps, ticked off as the work is done |
| **Customers** | What your own customers did on your customer surface |

### Choose who hears what

1. Open `/app/settings/notifications` (admins).
2. Under **To your team**, set each kind **In the app**, and its email to **Off**, **Straight away** or **In the daily digest**.
3. Under **Who**, give one person their own setting for that kind.
4. Under **To your customers**, **Edit** the message a customer receives and **Preview** it against one of your records.

Each kind ships with a setting. As a rule the critical ones email straight away, the important ones go in the daily digest and the rest stay in the app.

## Documents

URL: https://kabaido.ai/docs/parts/documents

Know which documents the platform renders, where to get each one and how they carry your brand.

Why: The documents a customer receives are the business in their hands, so they must be right.
What: Quotes, orders, dockets, labels, purchase orders and delivery notes, generated from the record and branded as yours.
How: Each PDF renders from the live record with your logo, brand colour and footer, in your document language.

### Where it appears

| Area | What you see | Brought by |
| --- | --- | --- |
| [Quotes](/docs/areas/quotes) | The quote PDF with your logo, colour and footer | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce and Source |
| [Orders](/docs/areas/orders) | An order confirmation on the quote's own template | Sales Engineer, Design Engineer, Service Centre, Wizard, Commerce, Route, Source and Machinist |
| [Suppliers](/docs/areas/suppliers) | Purchase order and RFQ PDFs for your suppliers | Source |
| [Catalogue](/docs/areas/catalogue) | A product image held on the catalogue record | Sales Engineer, Wizard, Commerce, Source and Stock |
| [Servicing](/docs/areas/servicing) | Dockets, labels in two sizes and a batch sheet | Service Centre |
| [Design](/docs/areas/design) | A spec sheet PDF, and STL, STEP, DXF and cutting lists | Design Engineer |
| [Route](/docs/areas/route) | Delivery notes, packing lists and collection notes, never priced | Route |
| [Commerce](/docs/areas/commerce) | A Documents page where customers download what you sent | Commerce |

### The documents

| Document | Where you get it |
| --- | --- |
| Quote | **PDF** on the quote in `/app/quotes`, and attached when you send it |
| Order confirmation | **PDF** on the order in `/app/orders` |
| Purchase order and request for quotation | On the purchase order or RFQ, for your supplier |
| Service docket, item and package labels, batch sheet | On the service item or batch in `/app/servicing` |
| Delivery note, packing list and collection note | On the delivery in `/app/route`; never priced |
| Load manifest | On a run, from Route's **Runs** or **Loading** view |
| Design spec sheet and files | From a design: a PDF spec sheet, and STL, GLB, STEP, DXF or a cutting list CSV where the design module supports it |
| Wizard spec sheet | On screen at the end of a wizard run, each line naming the chart it came from |

### Sending a quote

**Send** emails the contact the PDF and a link where they accept or decline. The body takes `{{number}}`, `{{company}}` and `{{valid_until}}`, and the email is logged against the quote.

### Branding by plan

Your logo and brand colour come from [Settings then Organisation](/docs/areas/settings#organisation) and apply on every plan.

| Plan | Documents carry |
| --- | --- |
| Free | Your logo and colour, plus a small **Prepared with Kabaido** footer and the Kabaido wordmark |
| Pro | White label: your logo and colour, no Kabaido footer or wordmark |
| Ultra | White label: your logo and colour, no Kabaido footer or wordmark |
| Max | White label: your logo and colour, no Kabaido footer or wordmark |

> Documents render in your organisation's document language: English, with a French rendering for organisations that work in French.

# Docs: Catalogue

## Schemas and fields

URL: https://kabaido.ai/docs/catalog/schemas-and-fields

Describe a product family with a schema of typed fields, and know which fields the AI matches an enquiry on.

Why: A product the AI cannot read field by field is a product it cannot match or filter.
What: A schema is the set of attributes one family of your products carries, on top of the core fields every product has.
How: Take one from the library, read one from your file or build your own on the Schemas view of `/app/catalog`.

### Core fields

Every product carries these, whatever its schema. Price and cost are stored in integer minor units (pence or cents).

| Key | Label | Needed |
| --- | --- | --- |
| `sku` | SKU | Required |
| `title` | Title | Required |
| `category` | Category | Optional |
| `uom` | Unit | Optional |
| `price` | Price | Optional |
| `cost` | Cost | Optional |
| `currency` | Currency | Optional |
| `stock_qty` | Stock | Optional |
| `lead_time_days` | Lead time (days) | Optional |

### Three ways to start a schema

| Choose | What happens |
| --- | --- |
| **Browse the library** | Adds an editable copy of a ready made schema. The library offers what your presets carry, or every schema when no preset is on. |
| **Build from a file** | Reads the columns of a price list or stock export into a schema for you to check. |
| **Build your own** | Starts empty, with a live preview of the product form and the filters. |

### Fields

A field has a **Label**, a **Key (snake_case)** such as `diameter_mm` and a **Type**: number, text, select, boolean or dimension. A number or dimension carries a **Unit**; a select carries its **Options (comma separated)**.

- **Synonyms (comma separated)** are the other names a column goes by (`dia`, `d1`). The import wizard maps headings with them.
- **Show in facet rail** puts the field in the grid's filters.
- **Required** marks the field. Only SKU and Title are enforced: a product without a required schema field is still saved.

### Match rules

A match rule tells the AI how a field decides a match. Only library schemas carry them (the field builder has no match controls); a schema card reads **matched by the AI** when it has them and **no match rules yet** when it does not.

| Role | Meaning |
| --- | --- |
| hard | The product must satisfy the requested value, or it is not a candidate. |
| soft | Counts towards the fit score by its weight, but never excludes. |
| ignore | Not used in matching. |

A numeric rule can carry a tolerance (absolute or a percentage) and a direction, such as meet or exceed. Equivalent values (TiAlN and AlTiN) come from Kabaido's knowledge packs or the field's own option aliases, never from a guess, and show as an alternative rather than an exact match.

> A schema read from a file never has match rules written for it: a rule decides what the AI will quote, so it is never inferred. Choose **Request a schema** in the library to have one built with its rules.


Schema changes are additive. Removing a field archives it and its values stay on the product; archiving a schema deletes nothing.

## Importing products

URL: https://kabaido.ai/docs/catalog/importing-products

Load a CSV or XLSX into your catalogue with the columns mapped for you, a checked sample and a run that resumes if it stops.

Why: Everything the AI quotes starts from a catalogue it can read.
What: The import wizard maps your file's columns to the core fields and a schema, checks a sample and loads it in batches.
How: Open the Imports view of `/app/catalog` and choose **New import**; imports are for admins and owners.

### Run an import

1. **Upload**: drop a CSV or XLSX (an XLSX reads its first sheet) and pick a **Target schema**, or **Core fields only**. **Download template CSV** gives you the headings.
2. **Map**: columns are matched by synonym and fuzzy match. Correct any that look wrong; SKU and Title are required. Name the mapping under **Saved mappings** to reuse it next time.
3. **Validate**: the first 500 rows are coerced exactly as the run will coerce them, listing unit conversions, duplicate SKUs and cells that hold no figure.
4. Choose the **Duplicate SKU policy**, **Update existing products** or **Skip duplicates**, then **Run import**.

### Check the money columns

Price and cost are separate targets. A heading such as cost price or buy price maps to cost, so a buy price never becomes what you sell at. A cell reading POA or Call imports empty, not as zero.

### When a run stops

- The run keeps its place. **Resume** carries on from the row it reached; rows already loaded are not loaded twice.
- **Cancel import** stops it cleanly, and what was loaded stays.
- Rows that fail are listed in **Download error report CSV** with the row and the reason.


> Before it loads a row, a run counts the new products the file would add (SKUs you already hold do not count). If they would pass your plan's product limit, the run is refused and nothing loads; see [plans and usage](/docs/billing/plans-and-usage).

## Bulk editing

URL: https://kabaido.ai/docs/catalog/bulk-editing

Change many products at once, from a few ticked rows to everything matching a filter, with an audit record of each run.

Why: A supplier's price rise or a renamed range touches hundreds of rows at once.
What: Bulk edit applies one change to a selection, on the server, in batches.
How: Select products on the Products view of `/app/catalog`, then choose **Bulk edit**; editing needs the engineer role or above.

### Select

- Tick the rows you want, or
- Filter with the facet rail, tick a row, then choose **Select all … matching**. It names the count, and the run covers the whole match set, not only the visible page. It is not offered while a text search is active.

### Choose one action

| Action | What it does |
| --- | --- |
| **Set a field value** | Writes one value to the title, category, unit or an attribute. |
| **Adjust price** | By **Percent (%)** or **Fixed amount**; a negative number decreases. **Round to** **No rounding**, **Nearest .00** or **Up to .95**. |
| **Find and replace** | Replaces text inside a field. |
| **Change category** | Moves the selection to a category. |
| **Change schema** | Moves the selection to a schema. |
| **Change status** | Active, Draft or Archived. |

One action a run keeps each change reviewable. Every run writes one audit record: the action, how many rows it touched, whether the selection was a filter, who ran it and when.

> Archive a discontinued line rather than deleting it. Archived products stay linked to past quotes and orders. Deleting is permanent: each line keeps its own snapshot, but its link back to the product is gone.

## Product groups

URL: https://kabaido.ai/docs/catalog/product-groups

Group products by category, schema or a saved view, and know which of those a price rule, a bulk edit or the API can target.

Why: Prices, edits and reports are set for sets of products, not one SKU at a time.
What: Kabaido groups products three ways: the category field, the schema and saved views of the grid.
How: Set the category and schema on import or with **Bulk edit**, and save a filter as a view on `/app/catalog`.

### What each grouping reaches

| Grouping | Set by | Used by |
| --- | --- | --- |
| Category | The `category` core field | Pricing rules and special prices, bulk edit, the `category` filter on the products API |
| Schema | The product's schema | Pricing rules and special prices, bulk edit, the facet rail |
| Saved view | **Views**, then a name for the current filters | Reopening a filtered grid and selecting all of it for a bulk edit. Kept for you alone, in this browser |

### Save a view

1. Filter the Products grid with the facet rail. A text search is not saved in a view.
2. Open **Views**, type a **View name** and choose **Save**.
3. Open the view later, tick a row and choose **Select all … matching** to act on every product in it.


> A price rule targets a single product, a category or a schema. A saved view is a filter, not a pricing scope: to price a set that is neither, give it a category first with **Change category**.

## Cost and margin

URL: https://kabaido.ai/docs/catalog/cost-and-margin

Give your products a cost so every quote line shows its margin, and know where that cost can come from.

Why: A discount on a line with no cost behind it is a margin nobody can see.
What: A product's cost is the `cost` core field, held in integer minor units beside its price.
How: Load it with a cost column on import, or accept it from supplier prices when Source is on.

### Set a product's cost

| Route | How |
| --- | --- |
| Import | Map a cost column (cost price, buy price, landed cost) on the Imports view. See [importing products](/docs/catalog/importing-products). |
| Supplier prices | On **Suppliers' prices**, select products and choose **Accept as cost**. The best active supplier price becomes the cost and the product records which supplier it came from. Needs Source and the engineer role or above. |

The products API and REST connections do not write cost, and the API never returns it.

### Margin on a quote line

When a product line is added, the product's cost is copied onto the line. The line then shows its margin under the amount, as a whole percentage: gross margin on the price after the line discount, `(price - cost) / price`. A negative margin shows in the danger colour.

A line with no cost shows no margin, never 100%. Margin is never markup.

> Changing a product's cost later does not rewrite quotes already raised: each line keeps the cost it was added with.

## REST connections

URL: https://kabaido.ai/docs/catalog/rest-connections

Pull products from your own REST API, map the fields once and refresh by hand or every night.

Why: A catalogue that is re-exported by hand goes stale.
What: A connection reads products from any REST endpoint that answers a GET with JSON.
How: Open `/app/catalog?tab=connections` and choose **New connection**; connections are for admins and owners.

### Set one up

1. Enter the **Name**, **Base URL** and **Endpoint path**.
2. Pick the **Authentication**: **Bearer token**, **Basic (user:pass)** or **Custom header** with its **Header name**. The credential is stored encrypted and never shown again.
3. Pick the **Pagination** (below) and the **Items path**, such as `data.items`, or leave it empty when the response is the array.
4. Choose **Test fetch**. The first item appears as JSON under **Sample item**: map against what you see.
5. Fill the **Field map** from JSON path to field, including **External ID**, pick the **Schedule** (**Manual** or **Daily**) and choose **Save connection**.

| Pagination | What Kabaido sends |
| --- | --- |
| **Single page** | One request. |
| **Page number** | A page parameter, advancing each request. |
| **Offset** | A row offset, advancing by the page size. |

Paging stops at an empty or short page. Each request has a time limit and a sync reads a capped number of pages, a guard against a feed that never ends.

### How records merge

A record whose external ID Kabaido already holds updates that product; any other is matched by SKU. Values are coerced against the schema exactly as on import. The connection card shows **Live**, **Paused** or **Failing**, the last run and how many items it synced.

## The products API

URL: https://kabaido.ai/docs/catalog/products-api

Push products into your catalogue from your own systems and read them back, with an API key.

Why: Some systems push rather than answer.
What: `POST /api/v1/products/bulk` upserts products by SKU and `GET /api/v1/products` lists them.
How: Create a key in [Settings, Integrations](/docs/areas/settings#integrations) with the `products:write` or `products:read` scope and send it as a Bearer token.

### Responses both endpoints share

| Status | When |
| --- | --- |
| 401 | No key, or not an organisation API key (they start `kbd_`). |
| 403 | The key lacks the scope. |
| 429 | The key is over its [rate limit](/docs/api/rate-limits). |

### Push products

The body is `{ schema_id?, products: [...] }`. Each product carries `sku` and `title` (required), any of `category`, `uom`, `price`, `currency`, `stock_qty` and `lead_time_days`, an `external_id`, and attributes in an `attrs` object or as top level keys that match the schema's fields. Coercion is the import wizard's.

```bash
curl -X POST https://kabaido.ai/api/v1/products/bulk \
 -H "Authorization: Bearer $KABAIDO_KEY" \
 -H "Content-Type: application/json" \
 -d '{ "schema_id": "<schema id>", "products": [ { "sku": "EM-12-4F", "title": "12 mm 4 flute end mill", "price": "42.50", "currency": "GBP", "attrs": { "diameter_mm": 12, "flutes": 4 } } ] }'
```

It answers `{ "upserted": n, "errors": [{ "index", "reason" }] }`, and a bad row never stops the rest.

Up to 10,000 products a call (more is 413). A call is refused with 402 before anything is written when the products you hold plus every product in it would pass your plan's product limit.

### List products

| Parameter | Behaviour |
| --- | --- |
| `search` | Matches title, SKU and category. |
| `sku`, `category` | Exact match. |
| `limit` | 1 to 500, default 100. |
| `cursor` | The `next_cursor` of the previous page; it is null on the last. |

Products come ordered by SKU with `id`, `sku`, `title`, `category`, `uom`, `price_minor`, `currency`, `stock_qty`, `lead_time_days`, `attrs`, `status`, `external_id`, `created_at` and `updated_at`. Cost is never returned.

> Money is stored in integer minor units (pence for GBP): the sample's `"price": "42.50"` is stored as a `price_minor` of 4250. Round half up only when you display it.

# Docs: Pricing and costing

## Pricing rules and the resolution order

URL: https://kabaido.ai/docs/pricing/pricing-rules-and-the-resolution-order

Know the exact order in which Kabaido reaches a unit price, so every line on every quote can be explained.

Why: The same product, for the same customer, at the same quantity must price the same whoever or whatever priced it.
What: One resolver prices every product, design and service line: the AI's draft quotes, the quote editor and the order editor.
How: It runs the four steps below in order and stores each step on the line.

### The order

1. **Base price.** A catalogue product's price; for a product priced by dimension, the price at the dimension asked for; for a saved design, the design worked out again at the line quantity; for a service line, the service's price.
2. **The customer's special price, one only.** Of the customer's special prices that fit the line and are in their dates, the most specific wins: product, then category, then schema, then the whole customer (a service line: service, then whole customer; a design line: whole customer only). A fixed price replaces the price; a percentage discounts it.
3. **One quantity break**, skipped when step 2 set a fixed price. Of the active rules on the most specific scope that fits the line, each offers its highest tier the quantity reaches; if several rules tie on that scope, the lowest price wins and the step says so.
4. **Floor at zero.** A rule that would take the price below nothing is floored at zero, as a visible step.

Two rules of one kind never stack. A special price and a quantity break do: the break applies to the special's result. The exception is a fixed special price, which is an agreed figure no break may move.

### Service and design lines

On a service line only a percentage special price applies; a fixed special price for that service is ignored. A line from a saved design takes a whole customer discount and no catalogue quantity rule: its quantity breaks live in the design itself.

### After the resolver

On the line itself a person can still set a discount, type a line total or type a unit price. A typed price is added to the chain as a manual step, so the steps above it are never lost.

### See how a line was priced

Choose the icon labelled **How this price was calculated** beside a quote line's price. It shows when a step changed the price, the price was typed or the line has a volume ladder. Each step shows its name and the change it made, and the chain is stored on the line, so it reads the same months later.


> Money is integer minor units (pence or cents). Each percentage step is rounded half up to a whole minor unit, and every total is rounded half up at display.

## Special prices and customer discounts

URL: https://kabaido.ai/docs/pricing/special-prices-and-brackets

Give one customer an agreed price on a product, a category or a schema, or a discount on everything they buy.

Why: A special price is about who is buying: the terms agreed with one account.
What: A special price is a percentage discount or a fixed price for one customer, on one scope, with optional dates.
How: Set it on the customer's record or on the Pricing view of the catalogue; both are for admins and owners.

### Set one on the customer

1. Open the customer at `/app/customers` and choose the **Special pricing** tab.
2. Pick the **Scope** and what it **Applies to**, then the **Kind**: **% discount** or **Fixed price**.
3. Enter the **Percent off** or the **Price**, and **Starts** and **Ends** if it has dates. The example line shows the effect on a base price before you choose **Add**.

The same rows appear on `/app/catalog?tab=pricing` under **Special prices**, where **New special price** starts with the **Customer**.

### Scopes

| Scope | Covers |
| --- | --- |
| Product | One catalogue product. |
| Category | Every product with that category. |
| Schema | Every product on that schema. |
| Service | Lines for one service; percentage only. |
| Whole customer | Every product, design and service line for the customer; percentage only, set from the customer record. |

The most specific scope that fits a line wins, so a product price beats a category discount, and a whole customer discount applies only where nothing narrower does. A **Configurator** special reaches no line today: a design line takes only the whole customer discount.

### With quantity breaks

A special price is about who; a [quantity rule](/docs/pricing/quantity-rules) is about how many. A percentage special and a break stack, special first. A fixed special price ends the chain.

> Removing a special price never changes a quote already priced with it. New lines for that customer go back to the standard price.

## Quantity rules

URL: https://kabaido.ai/docs/pricing/quantity-rules

Set a price ladder that lowers the unit price as the quantity rises, for a product, a category, a schema or a service.

Why: A hundred off costs less to supply than one, whoever orders it.
What: A pricing rule holds quantity breaks for every customer on one scope.
How: Open `/app/catalog?tab=pricing` and choose **New rule** under **Pricing rules**; rules are for admins and owners.

### Create a rule

1. Give it a **Name**, such as Volume discount, and pick the **Scope** (product, category, schema or service; a configurator rule reaches no line today) and what it **Applies to**.
2. Leave **Starts** and **Ends** empty for always on, or set the dates it runs between.
3. Under **Tiers**, enter a **Minimum quantity** and either a **% discount** or a **fixed price**. Choose **Add tier** for each further break.
4. Keep **Active** ticked and choose **Save rule**.

### How a tier applies

- The line takes the tier with the highest minimum quantity it reaches. Below the first tier, the rule does nothing.
- A percentage discounts the price after any percentage special price. A fixed price is the unit price at that quantity.
- Only the most specific scope's rules are considered, even when none of their tiers is reached, and only one rule applies: on a tie, the lowest price.
- Tiers are stored in ascending order, whatever order they were typed in.

### What the checks refuse

| Mistake | Message |
| --- | --- |
| No tiers | Add at least one quantity break. |
| A quantity of zero or a fraction | Break 1: the quantity must be a whole number of 1 or more. |
| A discount over 100% | Break 1: a discount is between 0% and 100%. |
| Two tiers on one quantity | Two breaks both start at 10. Each one needs its own quantity. |
| An end before the start | The end date is before the start date. |

### Where the ladder shows

A product line in the quote editor shows its **Volume price** ladder under **How this price was calculated**: only the quantities that beat the price for one. Tick **Show volume price breaks** on a quote to print the ladder on the PDF.

## Prices and margins at scale

URL: https://kabaido.ai/docs/pricing/margins-at-scale

Move the prices and costs of hundreds of products at once and keep sight of the margin while you do it.

Why: A supplier's increase or a new price file moves a whole range, not one SKU.
What: Kabaido moves prices by filter, by scope and by file, and reads the margin from cost on every line.
How: Pick the tool below that matches the change.

### Pick the tool

| The change | Use |
| --- | --- |
| Every price in a range goes up by a percentage | [Bulk edit](/docs/catalog/bulk-editing): filter with the facet rail, **Select all … matching**, **Adjust price** with **Round to**. |
| A new price file arrives | [Import](/docs/catalog/importing-products) it with **Update existing products** and a saved mapping. |
| Volume pricing for a whole family | A [quantity rule](/docs/pricing/quantity-rules) on the category or the schema. |
| One account's terms | A [special price](/docs/pricing/special-prices-and-brackets) on a category or schema, or a whole customer discount. |
| Supplier prices have moved | **Accept as cost** on **Suppliers' prices** for every product selected. |

### Keep the margin in sight

A catalogue price is always a figure you set; nothing reprices the catalogue from a target margin. The margin is read from the price and the cost, so load cost first and every new product line shows it.

With Source on, activating a supplier price list tells the buyers how many products' best price moved beyond the alert threshold, and an organisation can choose to accept those prices as cost automatically.

> A bulk price change applies to the catalogue from then on. Quotes already raised keep their prices and their costs.

## Where cost comes from

URL: https://kabaido.ai/docs/pricing/where-cost-comes-from

Know every place a cost enters the platform, what each one costs and what happens when a figure is missing.

Why: A margin is only as true as the cost under it.
What: Every cost is built from something with a source: a cost field, a received price, a rate or a stock movement.
How: Each product that does work brings its own cost, listed below.

### The sources

| What is costed | Where the cost comes from | Set in |
| --- | --- | --- |
| A catalogue product | The cost field, from an import or an accepted supplier price | [Cost and margin](/docs/catalog/cost-and-margin) |
| Goods received | The landed unit cost on a posted goods in, which moves the stock line's moving average | [Goods in](/docs/source/goods-in) |
| Stock | The moving average on each stock line | [Items and balances](/docs/stock/items-and-balances) |
| A serviced item | Rates and standard minutes, then the minutes actually recorded | [Cost against time](/docs/service-centre/cost-against-time) |
| A machined job | The machine, the person and the material the run consumed | [Costs](/docs/machinist/costs) |
| A line from a saved design | None: the design module's rates set its price, so the line carries no cost and shows no margin | [Rates and stock](/docs/design-engineer/stock-modes) |

### Rates

A rate (labour an hour, machine an hour, overhead and the rest) is held for the organisation, a centre, a station, a machine or an operator, with the dates it applied. A rate rise never rewrites last month's costs.

> There is no default labour or machine rate. A Machinist cost with a missing rate reads **No rate**, and a line with no cost shows no margin: missing is said as missing, never as zero.

### Who sees cost

Costs and margins in Servicing, Machinist and Suppliers' prices are for the engineer role and above. An operator never sees a price, a cost or a margin.

## Margin reporting

URL: https://kabaido.ai/docs/pricing/margin-reporting

Read margin by line, by service, by job, by customer and by month, from the one definition the whole platform uses.

Why: Margin is where a price meets the cost of doing the work.
What: Margin is always gross margin on the sell price, `(price - cost) / price`, never markup.
How: Read it on the quote line, in the Servicing reports and on Machinist costs.

### Where to read it

| Where | What it shows |
| --- | --- |
| A quote line | The line's margin after its discount, as a whole percentage, under the amount. |
| `/app/servicing?view=costing`, **Cost and margin** | Standard against actual cost, price, margin and margin per cent. |
| `/app/machinist/costs` | Each job's machine, labour and material cost, standard against actual, and its margin. |

### Run the servicing report

1. Open the Costing view of Servicing and choose **Cost and margin**.
2. Pick **Group by**: Step, Station group, Service, Family, Centre, Customer or Month, and the **From** and **To** dates.
3. Choose **Run**, then **Export CSV** to take the rows away.

### Machinist costs

Switch between **By job**, **By machine**, **By operator** and **By month**. A job's margin needs the order line it was raised from; material is what the run consumed at the stock line's moving average.

> A margin with no cost behind it is left empty rather than shown as 100%. Money is held in integer minor units and rounded half up only at display.

# Docs: Integrations

## Connecting other systems

URL: https://kabaido.ai/docs/integrations/connecting-other-systems

Read any integration's label correctly and pick the right path for a system that has no named connection.

Why: Your workshop already runs systems, and Kabaido has to meet them rather than replace them.
What: One catalogue of every connection, each with one of four labels, plus generic paths that reach any system with an API.
How: Open `/app/settings/integrations`, search for what you run and open its entry.

Screenshot of /app/settings/integrations: Settings then Integrations: every connection grouped by kind, each with its status label.

### The four labels

Every entry carries exactly one label, on the website and in Settings alike. Nothing is labelled **Works today** unless Kabaido code talks to the provider.

| Label | What it means |
| --- | --- |
| **Works today** | Kabaido code talks to the provider. |
| **Template** | A prepared recipe on a generic path, which you finish. |
| **Via automation** | Through Zapier, Make or n8n. |
| **Roadmap** | Not built yet. Tell us what you need and we will talk it through. |

### Finding an entry

1. Open `/app/settings/integrations`. Every connection sits in one list with a search box, a type filter and the **All**, **Active**, **Suggested** and **New** chips.
2. Open an entry. Its panel says what it is for, walks through the setup and, once connected, manages it: keys, endpoints, deliveries or receipts.
3. A link ending `?open=<id>` opens one panel directly, which is how prompts elsewhere in the platform send you there.

Connecting needs the admin role or above. No plan gates a connection; an entry tied to a product, such as the Inspect contact finders, needs that product switched on.

### The universal paths

When your system has no named entry, one of these reaches it. Most setups use two or three together.

| If your system | Use |
| --- | --- |
| Can be programmed against an API | [The REST API](/docs/api/the-rest-api) with a scoped key, or [the MCP server](/docs/api/mcp) for an AI assistant. |
| Needs to hear when something happens here | [Outbound webhooks](/docs/api/webhooks): signed JSON posted to your URL. |
| Can send but not receive | [An inbound endpoint](/docs/api/inbound-endpoints): a tokenised URL it posts JSON to. |
| Answers a GET request from the internet | A scheduled REST pull: [customers](/docs/integrations/customer-connections) or [products](/docs/catalog/rest-connections), daily or by hand. |
| Is a person with a spreadsheet | [CSV import and export](/docs/integrations/csv-import-export-reference), on every plan. |
| Already runs an automation tool | [Zapier](/docs/integrations/zapier), [Make](/docs/integrations/make) or [n8n](/docs/integrations/n8n): webhooks start a flow and the flow writes back over the API. |

> A **Roadmap** entry is not built. Its page says what it would do; [tell us](/contact) what you need, and meanwhile the paths above cover the same data.

## Customer connections

URL: https://kabaido.ai/docs/integrations/customer-connections

Pull your customer list from a CRM or ERP over REST, mapped once and refreshed every night or when you ask.

Why: Your customer list already lives in a CRM or an ERP, and keeping a second copy in step by hand is where mistakes start.
What: A customer connection reads that list over HTTP and creates or updates the customers in `/app/customers`.
How: Set it up on the **Custom REST connection** entry, or on a Template entry such as [HubSpot](/docs/integrations/hubspot) that carries the recipe for that system.

### Set one up

1. In `/app/settings/integrations`, open **Custom REST connection** and choose **New connection**. It needs the admin role.
2. Give the **Base URL** and **Endpoint path**. Pick **Authentication**: **Bearer token**, **Basic (user:pass)** or **Custom header** (the header name defaults to `x-api-key`). The credential is stored encrypted.
3. Set the **Records path** to the array inside the response, such as `data.customers`, or leave it empty when the response is the array.
4. Press **Test fetch** to see a sample record, then fill the **Field map** with dotted paths: **Company field** (required), **Email field**, **Phone field** and **External ID field**.
5. Choose the **Schedule**, **Daily** or **Manual**, and **Save connection**.

The source answers one GET request with JSON. There is no paging: the whole list comes back in one response.

### How records merge

1. By external id, when you mapped one. It survives a company being renamed.
2. Otherwise by the email domain of the mapped email.

A match updates the customer's company name and email domain. No match creates a customer, with the email or phone as its primary contact. A record with no company is skipped.

> A connection never deletes. A customer missing from the source stays in Kabaido until you remove it, and deleting the connection keeps every customer it brought in.

### Running and watching

Daily connections run in the overnight sync; **Run now** runs one at once. Each run gives the source 20 seconds. A run that cannot fetch or read the list records its error on the connection and changes no customer.

> A failed **Run now** marks the connection as errored, and the overnight sync skips it until you save it again.

If your system cannot be reached from the internet, reverse the direction: an [inbound endpoint](/docs/api/inbound-endpoints) set to **Upsert customers** merges by the same rules.

## Booking a meeting

URL: https://kabaido.ai/docs/integrations/scheduling

Book a call with the Kabaido team from the platform or the website, and move or cancel it without an email exchange.

Why: Arranging a call by email takes days; picking a free time takes a minute.
What: A picker over the Kabaido team's real calendar that books a Google Meet and sends Google's own invitation.
How: Press **Book a walkthrough** or **Book a meeting**, pick a day and a time, and press **Book the meeting**.

The buttons sit on the website header, `/contact` and `/pricing`, and in the platform on the Commerce website screens, `/app/machinist`, `/app/wizard`, Support, the Enterprise card in `/app/settings/billing` and the custom build cards in `/app/settings/presets`.

### What you are offered

- 30 minute meetings between 09:00 and 16:00 UK time, Monday to Friday. Weekends and England and Wales bank holidays are never offered.
- At least three business days ahead, across a three week window.
- At most three start times a day. They vary from day to day and stay the same each time you look at one day.
- A calendar event blocks its time when it has another attendee who has not declined, is all day or is marked out of office. Cancelled events, timed events marked free and working location entries never block.
- Every blocking event carries fifteen minutes either side, so nothing is offered back to back.
- Meetings already booked through Kabaido block their time too, so two people cannot take the same slot.

Times are computed in Europe/London and stay right across the clock changes. The picker shows each time in your own time zone, with the London time beside it when they differ.

### The meeting

Google creates the Google Meet link with the calendar event and sends the invitation, so the entry in your calendar is Google's own. A confirmation email follows with the link and a manage link of your own.

### Moving or cancelling

The manage link opens the meeting with no account or password. Move it to another free time and the calendar entry updates in place, keeping the same Google Meet link; cancel it and the entry is removed.

### When no times load

The picker says so and offers a message to the team instead. It never shows invented availability. Booking draws no usage.

## CSV import and export

URL: https://kabaido.ai/docs/integrations/csv-import-export-reference

Move data in and out of Kabaido with CSV, and know what the parser accepts before you upload.

Why: Every business has spreadsheets, and CSV is the integration that needs no integration.
What: A product import wizard, a customer import dialog and an **Export** control on the lists.
How: Choose **Import CSV** in `/app/catalog` or `/app/customers`, and **Export** above any list.

### What the parser accepts

- Comma, semicolon, tab and pipe delimiters, sniffed from the header line, so a semicolon file needs no setting.
- Double quoted fields, with a doubled quote for a literal one. Delimiters and line breaks inside quotes are safe.
- CRLF and LF line endings alike.
- XLSX workbooks, converted to CSV in your browser; the first sheet is used.

> Save your own files as UTF-8. The wizard's blank template carries a byte order mark so Excel opens it as UTF-8.

### Importing products

1. In `/app/catalog`, choose **Import CSV**, upload the file and pick the schema. Importing needs the admin role.
2. Map each column to a core field or a schema attribute. SKU and title must be mapped; unmapped columns are ignored.
3. Validate: the first 500 rows are checked and the problems are listed by row and column.
4. Choose to update or skip SKUs that already exist, then run.

| Validation reports | Meaning |
| --- | --- |
| Error | The cell will not convert to the field's type. The row still imports with that cell empty. |
| Note | The cell holds no figure (POA, N/A). Not an error and never a zero. |
| Warning | The price mapping looks wrong: no column mapped to Price, or a money column left unmapped. |
| Unit hint | A value looks like a different unit from the field's. |

The run works in batches of 1,000 rows and records its place after each, so an interrupted import resumes where it stopped and no row is written twice. An error report CSV lists the cells that had something to say. A mapping can be saved and reused for the next file.

### Importing customers

In `/app/customers`, **Import CSV** takes company, contact, email, phone and terms columns in any order, mapped by heading. **Download a sample CSV** shows the shape. A preview counts new rows and possible duplicates (by email domain and company name) and offers to skip them.

### Exporting

See [Export your data](/docs/integrations/export-your-data).

## Export your data

URL: https://kabaido.ai/docs/integrations/export-your-data

Get the records you put into Kabaido back out, and know which route gives you which.

Why: Your data is yours, and getting it out should not need a support ticket.
What: An **Export** control on the lists, the REST API for feeds, and a full export on request.
How: Choose **Export** above a list, or page a resource over the API.

### From a list

1. Filter the list to what you want. **Export** takes exactly what the table shows.
2. Choose **Export**, then the rows (**Filtered**, or **Shown** when nothing is filtered, or **Everything loaded**), the **Columns** and the **File name**.
3. Pick CSV, which opens in Excel and Google Sheets, or JSON, which keeps the raw values, and press **Download**.

The control shows the row and column count before you download, and warns when only part of the table has loaded yet.

It sits above Quotes (with its **Supplier** view), Orders (with its **Purchase** and **Deliveries** views), Customers, Suppliers and the Stock lines, movements and reorder views.

### The catalogue, over the API

The catalogue has no export button. [The products API](/docs/catalog/products-api) pages every product with its attributes as JSON, ordered by SKU, until `next_cursor` comes back null.

> Want a one off spreadsheet of the catalogue rather than a feed? [Ask us](/contact) and we will produce it.

### Everything, on request

A complete export of your organisation's data is available whenever you ask, in a machine readable form. Deletion is a separate request: see [data export and deletion](/docs/security/data-export-and-deletion).

Exports keep your own identifiers: SKUs, attribute keys and quote and order numbers, so the data is useful elsewhere without translation.

## Email agent

URL: https://kabaido.ai/docs/integrations/email-agent

Enquiries that arrive by email become requests with a drafted reply, without anyone forwarding anything into Kabaido.

Reads your connected inbox, turns each RFQ and purchase order into a request and drafts a branded reply.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Email |
| For | Every workspace |

### What you get

Enquiries that arrive by email become requests with a drafted reply, without anyone forwarding anything into Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Connect a Gmail or Microsoft 365 inbox and approve the sign in.
2. Set review mode and the internal address drafts go to.
3. Watch the first days of classifications and corrections.
4. Switch the inbox to direct sending once you are satisfied.

### More

- The full guide: [the email agent](/docs/sales-engineer/the-email-agent).
- On the website: [Email agent](/integrations/email-agent).

## Claude

URL: https://kabaido.ai/docs/integrations/claude

Ask Claude about your own catalogue, quotes and orders, and raise a request from the answer.

Search your catalogue, read quotes and orders and raise requests from Claude over MCP.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | AI assistants |
| For | Every workspace |

### What you get

Ask Claude about your own catalogue, quotes and orders, and raise a request from the answer.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Open Claude settings, then Connectors, then Add custom connector.
2. Paste your organisation's MCP URL and approve the Kabaido sign in.
3. Pick the organisation and the scopes to grant.
4. Ask Claude about your catalogue, your quotes and your orders.

### More

- On the website: [Claude](/integrations/claude).
- The provider's own documentation: [support.claude.com](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp).

## Any MCP client

URL: https://kabaido.ai/docs/integrations/mcp

Any MCP client your team already runs reads the same org-scoped tools, under the scopes you grant.

Claude Code, Cursor and any other MCP client connect with an API key over streamable HTTP.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | AI assistants |
| For | Every workspace |

### What you get

Any MCP client your team already runs reads the same org-scoped tools, under the scopes you grant.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Copy the server URL from the panel below.
2. Create an API key with the scopes the client should have.
3. Add the server to the client with an Authorization: Bearer header.

### More

- The full guide: [mcp](/docs/api/mcp).
- On the website: [Any MCP client](/integrations/mcp).

## Slack

URL: https://kabaido.ai/docs/integrations/slack

The channel your team already watches sees a quote sent, an order raised or a service due as it happens.

Post quote, order and service events into a channel as readable messages.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Messaging |
| For | Every workspace |

### What you get

The channel your team already watches sees a quote sent, an order raised or a service due as it happens.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In Slack create an incoming webhook for the channel you want.
2. Paste the webhook URL here and choose the events to send.
3. Wait for the next chosen event, such as a quote being sent, and check how it reads in the channel. Its delivery shows under Recent deliveries on the endpoint.
4. Add a second endpoint for a different channel where the audience differs.

### More

- On the website: [Slack](/integrations/slack).
- The provider's own documentation: [api.slack.com](https://api.slack.com/messaging/webhooks).

## Microsoft Teams

URL: https://kabaido.ai/docs/integrations/teams

The same events as Slack, posted into a Teams channel as Adaptive Cards.

Send events into a Teams channel as Adaptive Cards through a Workflows webhook.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Messaging |
| For | Every workspace |

### What you get

The same events as Slack, posted into a Teams channel as Adaptive Cards.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In Teams add the Workflows app to your channel and pick the webhook template.
2. Copy the request URL the workflow gives you and paste it here.
3. Choose the events to send, then check the first card that arrives in the channel. Its delivery shows under Recent deliveries on the endpoint.
4. Add a second endpoint for a different channel where the audience differs.

### More

- On the website: [Microsoft Teams](/integrations/teams).
- The provider's own documentation: [support.microsoft.com](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498).

## Zapier

URL: https://kabaido.ai/docs/integrations/zapier

Kabaido events reach the thousands of apps Zapier already connects, with no code on either side.

Trigger Zaps from signed webhooks and write back through the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Automation platforms |
| For | Every workspace |

### What you get

Kabaido events reach the thousands of apps Zapier already connects, with no code on either side.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In Zapier create a Zap with the Webhooks by Zapier trigger and copy the hook URL.
2. Add it here as an outbound endpoint and choose the events to send.
3. Map the payload onto the action you want in your Zap.
4. For the other direction, use Webhooks by Zapier actions against the Kabaido API with an API key.

### More

- On the website: [Zapier](/integrations/zapier).
- The provider's own documentation: [zapier.com](https://zapier.com/apps/webhook/integrations).

## Make

URL: https://kabaido.ai/docs/integrations/make

A Make scenario runs on every Kabaido event and writes back through the API.

Start Make scenarios from Kabaido events and post data back over HTTP modules.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Automation platforms |
| For | Every workspace |

### What you get

A Make scenario runs on every Kabaido event and writes back through the API.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In Make add a Custom webhook trigger and copy its URL.
2. Add it here as an outbound endpoint and choose the events to send.
3. Map the payload onto the steps you want to run.
4. Use Make's HTTP module with a Kabaido API key for actions back into Kabaido.

### More

- On the website: [Make](/integrations/make).
- The provider's own documentation: [www.make.com](https://www.make.com/en/help/tools/webhooks).

## n8n

URL: https://kabaido.ai/docs/integrations/n8n

Your self-hosted n8n receives Kabaido events and drives whatever runs behind your firewall.

Self hosted automation: webhook triggers in, HTTP request nodes back to the API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Automation platforms |
| For | Every workspace |

### What you get

Your self-hosted n8n receives Kabaido events and drives whatever runs behind your firewall.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In n8n add a Webhook node and copy its production URL.
2. Add it here as an outbound endpoint and choose the events to send.
3. Map the payload onto the nodes you want to run.
4. Use the HTTP Request node with a Kabaido API key for actions back into Kabaido.

### More

- On the website: [n8n](/integrations/n8n).
- The provider's own documentation: [docs.n8n.io](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/).

## Dynamics 365 Business Central

URL: https://kabaido.ai/docs/integrations/dynamics365

Your Business Central customer list is the one Kabaido quotes against, refreshed daily.

Pull customers from Microsoft Dynamics 365 Business Central on a scheduled REST connection, and let Microsoft Dynamics 365 Business Central post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |

### What you get

Your Business Central customer list is the one Kabaido quotes against, refreshed daily.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in Microsoft Dynamics 365 Business Central as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so Microsoft Dynamics 365 Business Central can post progress back.

### More

- On the website: [Dynamics 365 Business Central](/integrations/dynamics365).
- The provider's own documentation: [learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/web-services).

## EFACS E/8

URL: https://kabaido.ai/docs/integrations/efacs

Customers come out of EFACS and order status returns as it changes.

Pull customers from EFACS E8 over its web service, and let EFACS post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer) and [Stock](/docs/stock) |

### What you get

Customers come out of EFACS and order status returns as it changes.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In EFACS expose customers over the SOA web service as one JSON response, and note the endpoint and the credential.
2. Create a REST connection here with that endpoint and map the company, the email and the customer code.
3. Run the test fetch and read the sample rows.
4. Add an inbound endpoint with the ERP order status action so EFACS can post progress back in its own status words.

### More

- On the website: [EFACS E/8](/integrations/efacs).
- The provider's own documentation: [www.exel.co.uk](https://www.exel.co.uk/efacs-e-8/).

## NetSuite

URL: https://kabaido.ai/docs/integrations/netsuite

Quote against the customer accounts Oracle NetSuite already holds, rather than a copy somebody retyped.

A SuiteScript in Oracle NetSuite posts customer records and order status to Kabaido inbound endpoints.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |

### What you get

Quote against the customer accounts Oracle NetSuite already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an inbound endpoint below and copy its URL and signing secret.
2. In Oracle NetSuite, add a SuiteScript that posts each new or changed customer record to that URL, in the documented shape for the upsert customers action.
3. Watch the receipts under the endpoint to confirm each post landed.
4. For order progress, add a second endpoint with the ERP order status action and have the script post status changes to it.

### More

- On the website: [NetSuite](/integrations/netsuite).

## SAP Business One

URL: https://kabaido.ai/docs/integrations/sap

Quote against the customer accounts SAP Business One already holds, rather than a copy somebody retyped.

Your SAP Business One middleware writes customers and products through the Kabaido API and reads quotes and orders back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |

### What you get

Quote against the customer accounts SAP Business One already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with only the scopes your middleware needs.
2. From that middleware, write SAP Business One customers and products to the Kabaido REST API, and read quotes and orders back.
3. Add an outbound endpoint under Custom outbound webhook so SAP Business One hears about each quote and order event as it happens.

### More

- On the website: [SAP Business One](/integrations/sap).

## Odoo

URL: https://kabaido.ai/docs/integrations/odoo

Quote against the customer accounts Odoo already holds, rather than a copy somebody retyped.

Your own Odoo code or middleware writes customers and products through the Kabaido API and reads quotes and orders back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |

### What you get

Quote against the customer accounts Odoo already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with only the scopes your Odoo integration needs.
2. From your own middleware or custom Odoo code, write customers and products to the Kabaido REST API, and read quotes and orders back.
3. Add an outbound endpoint under Custom outbound webhook so Odoo hears about each quote and order event as it happens.

### More

- On the website: [Odoo](/integrations/odoo).

## Xero

URL: https://kabaido.ai/docs/integrations/xero

An order ready to invoice becomes a Xero invoice through your automation, without anyone retyping it.

Send order events to Xero through Zapier, Make or n8n, and record the invoice reference it raises.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |

### What you get

An order ready to invoice becomes a Xero invoice through your automation, without anyone retyping it.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint for the order events under Zapier, Make or n8n, pointed at that platform's hook.
2. In the automation, raise the invoice in Xero from the payload.
3. Add an inbound endpoint with the order invoice action under Invoice status from any package, and give its URL to the automation.
4. Have the automation post the invoice reference and the paid state back, and the order shows them.

### More

- On the website: [Xero](/integrations/xero).

## QuickBooks

URL: https://kabaido.ai/docs/integrations/quickbooks

The same invoice lane as Xero, through the automation platform you already run.

Send order events to QuickBooks Online through Zapier, Make or n8n, and record the invoice reference it raises.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |

### What you get

The same invoice lane as Xero, through the automation platform you already run.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint for the order events under Zapier, Make or n8n, pointed at that platform's hook.
2. In the automation, raise the invoice in QuickBooks Online from the payload.
3. Add an inbound endpoint with the order invoice action under Invoice status from any package, and give its URL to the automation.
4. Have the automation post the invoice reference and the paid state back, and the order shows them.

### More

- On the website: [QuickBooks](/integrations/quickbooks).

## Sage

URL: https://kabaido.ai/docs/integrations/sage

Stop the retyping between the order and the invoice. Sage 50 Accounts stays the system of record and Kabaido records the reference.

Send order events to Sage 50 Accounts through Zapier, Make or n8n, and record the invoice reference it raises.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source), [Stock](/docs/stock) and [Commerce](/docs/commerce) |

### What you get

Stop the retyping between the order and the invoice. Sage 50 Accounts stays the system of record and Kabaido records the reference.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint for the order events under Zapier, Make or n8n, pointed at that platform's hook.
2. In the automation, raise the invoice in Sage from the payload, and give it a Kabaido API key if it needs to read the order behind an event.
3. Add an inbound endpoint with the order invoice action under Invoice status from any package, and give its URL to the automation.
4. Have the automation post the invoice reference and the paid state back, and the order shows them.

### More

- On the website: [Sage](/integrations/sage).

## HubSpot

URL: https://kabaido.ai/docs/integrations/hubspot

The companies in HubSpot are the customers in Kabaido, refreshed daily and matched on domain.

Pull companies from the HubSpot CRM into Customers with a scheduled REST connection.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | CRM |
| For | [Sales Engineer](/docs/sales-engineer), [Service Centre](/docs/service-centre), [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |

### What you get

The companies in HubSpot are the customers in Kabaido, refreshed daily and matched on domain.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a HubSpot private app with read access to companies and copy its token.
2. Create a REST connection here with the companies endpoint and that token.
3. Map the company name and the domain, then run the test fetch.
4. Schedule the daily sync and check the first run.

### More

- On the website: [HubSpot](/integrations/hubspot).
- The provider's own documentation: [developers.hubspot.com](https://developers.hubspot.com/docs/api/crm/companies).

## Salesforce

URL: https://kabaido.ai/docs/integrations/salesforce

Quote against the accounts your sales team already keeps, and let Salesforce see what happened to the enquiry without anyone copying it across.

Through Zapier, Make or n8n: quote and order events go out to Salesforce, and accounts come back into Customers.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | CRM |
| For | [Sales Engineer](/docs/sales-engineer), [Wizard](/docs/wizard) and [Inspect](/docs/inspect) |

### What you get

Quote against the accounts your sales team already keeps, and let Salesforce see what happened to the enquiry without anyone copying it across.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint for the quote and order events under Zapier, Make or n8n, pointed at that platform's hook.
2. In the automation, write each event onto the matching Salesforce record.
3. For accounts coming the other way, add an inbound endpoint with the upsert customers action under Custom inbound endpoint.
4. Have the automation map each new or changed Salesforce account onto the documented shape and post it to that URL, and it appears in Customers.

### More

- On the website: [Salesforce](/integrations/salesforce).

## Apollo

URL: https://kabaido.ai/docs/integrations/apollo

An open company profile in Inspect names the people to call: a free preview of who works there, then a reveal that returns the address and phone from your own Apollo account.

Find and reveal contacts on your own Apollo account, connected once with OAuth.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

An open company profile in Inspect names the people to call: a free preview of who works there, then a reveal that returns the address and phone from your own Apollo account.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. An org admin presses Connect and approves the Kabaido app in Apollo.
2. The Apollo user who approves it needs the third party apps permission. Ask an Apollo admin if yours does not have it.
3. Come back here and press Check. It names the Apollo account you are connected as; Apollo reports no balance through this connection, so none is shown.
4. Open a company profile in Inspect, then find and reveal contacts on its Contacts tab.

### More

- The full guide: [connectors](/docs/inspect/connectors).
- On the website: [Apollo](/integrations/apollo).

## Lemlist

URL: https://kabaido.ai/docs/integrations/lemlist

A list built in Inspect goes straight into a Lemlist campaign without a CSV in between.

Database search, async enrichment and campaign pushes on your own Lemlist account.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

A list built in Inspect goes straight into a Lemlist campaign without a CSV in between.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an API key in Lemlist under Settings, Integrations.
2. Paste it below; it is stored encrypted and never leaves the platform.
3. Push a list to a campaign from any Inspect list.

### More

- The full guide: [connectors](/docs/inspect/connectors).
- On the website: [Lemlist](/integrations/lemlist).

## Clay

URL: https://kabaido.ai/docs/integrations/clay

Clay's waterfall enrichment runs on Inspect companies and the answers come back into the profile.

Push companies to a Clay table; enriched rows return through the callback URL.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

Clay's waterfall enrichment runs on Inspect companies and the answers come back into the profile.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Clay table with a webhook source and copy its URL.
2. Paste your Clay API key and that webhook URL below.
3. Push companies from an Inspect list and watch the rows return.

### More

- The full guide: [connectors](/docs/inspect/connectors).
- On the website: [Clay](/integrations/clay).

## Hunter

URL: https://kabaido.ai/docs/integrations/hunter

It would preview the people at a domain and reveal only the ones you choose, on your own Hunter account, with the address never appearing in a preview.

Not available yet. The Hunter connector is written but held switched off until its redistribution terms are cleared in writing.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

It would preview the people at a domain and reveal only the ones you choose, on your own Hunter account, with the address never appearing in a preview.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Hunter](/integrations/hunter).

## Prospeo

URL: https://kabaido.ai/docs/integrations/prospeo

The cheapest of the finders, used when the others come back empty.

Budget domain search and reveals, charged only on a success.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

The cheapest of the finders, used when the others come back empty.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Copy your API key from the Prospeo dashboard.
2. Paste it below; it is stored encrypted.
3. Prospeo joins the fallback order behind Apollo.

### More

- The full guide: [connectors](/docs/inspect/connectors).
- On the website: [Prospeo](/integrations/prospeo).

## Anymailfinder

URL: https://kabaido.ai/docs/integrations/anymailfinder

A last resort finder that only bills when the address is verified.

Budget reveals by name and domain, charged only on a verified address.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | Every workspace |

### What you get

A last resort finder that only bills when the address is verified.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Copy your API key from the Anymail Finder dashboard.
2. Paste it below; it is stored encrypted.
3. It joins the fallback order behind the other finders.

### More

- The full guide: [connectors](/docs/inspect/connectors).
- On the website: [Anymailfinder](/integrations/anymailfinder).

## Outreach suppression

URL: https://kabaido.ai/docs/integrations/outreach-suppression

A customer who asked not to be contacted stays uncontacted, whichever finder or list they turn up in.

Addresses and domains no Inspect outreach ever goes to, however a list was built.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |

### What you get

A customer who asked not to be contacted stays uncontacted, whichever finder or list they turn up in.

### More

- The full guide: [outreach and compliance](/docs/inspect/outreach-and-compliance).
- On the website: [Outreach suppression](/integrations/outreach-suppression).

## Labels and tracking connector

URL: https://kabaido.ai/docs/integrations/courier-labels

It would let your own carrier account or despatch aggregator book the consignment, return the label and report the tracking, without anybody retyping a reference.

Not built yet. A connector that books the consignment, returns the label and polls the tracking on your own carrier or aggregator account, with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |

### What you get

It would let your own carrier account or despatch aggregator book the consignment, return the label and report the tracking, without anybody retyping a reference.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Labels and tracking connector](/integrations/courier-labels).

## Royal Mail

URL: https://kabaido.ai/docs/integrations/royal-mail

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Not connected to your Royal Mail account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Royal Mail account number. Kabaido holds no Royal Mail credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Royal Mail](/integrations/royal-mail).

## Parcelforce

URL: https://kabaido.ai/docs/integrations/parcelforce

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Not connected to your Parcelforce account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Parcelforce account number. Kabaido holds no Parcelforce credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Parcelforce](/integrations/parcelforce).

## DPD

URL: https://kabaido.ai/docs/integrations/dpd

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Not connected to your DPD account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own DPD account number. Kabaido holds no DPD credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [DPD](/integrations/dpd).

## DHL Express

URL: https://kabaido.ai/docs/integrations/dhl-express

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Not connected to your DHL Express account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own DHL Express account number. Kabaido holds no DHL Express credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [DHL Express](/integrations/dhl-express).

## DHL eCommerce

URL: https://kabaido.ai/docs/integrations/dhl-ecommerce

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your DHL eCommerce account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own DHL eCommerce account number. Kabaido holds no DHL eCommerce credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [DHL eCommerce](/integrations/dhl-ecommerce).

## UPS

URL: https://kabaido.ai/docs/integrations/ups

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your UPS account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own UPS account number. Kabaido holds no UPS credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [UPS](/integrations/ups).

## FedEx

URL: https://kabaido.ai/docs/integrations/fedex

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your FedEx account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own FedEx account number. Kabaido holds no FedEx credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [FedEx](/integrations/fedex).

## Evri

URL: https://kabaido.ai/docs/integrations/evri

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your Evri account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Evri account number. Kabaido holds no Evri credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Evri](/integrations/evri).

## DX

URL: https://kabaido.ai/docs/integrations/dx

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your DX account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own DX account number. Kabaido holds no DX credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [DX](/integrations/dx).

## APC Overnight

URL: https://kabaido.ai/docs/integrations/apc-overnight

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your APC Overnight account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own APC Overnight account number. Kabaido holds no APC Overnight credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [APC Overnight](/integrations/apc-overnight).

## Palletways

URL: https://kabaido.ai/docs/integrations/palletways

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Not connected to your Palletways account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Palletways account number. Kabaido holds no Palletways credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Palletways](/integrations/palletways).

## Pall-Ex

URL: https://kabaido.ai/docs/integrations/pall-ex

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route), [Source](/docs/source) and [Service Centre](/docs/service-centre) |
| What moves | Not connected to your Pall-Ex account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Pall-Ex account number. Kabaido holds no Pall-Ex credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Pall-Ex](/integrations/pall-ex).

## The Pallet Network (TPN)

URL: https://kabaido.ai/docs/integrations/tpn

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your TPN account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own TPN account number. Kabaido holds no TPN credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [The Pallet Network (TPN)](/integrations/tpn).

## Palletline

URL: https://kabaido.ai/docs/integrations/palletline

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your Palletline account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Palletline account number. Kabaido holds no Palletline credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Palletline](/integrations/palletline).

## Fortec

URL: https://kabaido.ai/docs/integrations/fortec

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

Record the service, the consignment reference and the packages by hand, print or upload the carrier's own label, and the tracking link renders from your own template. A connection to this carrier's account that books and tracks on its own is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Source](/docs/source) |
| What moves | Not connected to your Fortec account yet. The consignment, packages and tracking reference are recorded against the order by hand. |
| What you hand over | Your own Fortec account number. Kabaido holds no Fortec credential. |

### What you get

Consignments with this carrier are on the order, on the delivery note and on the customer's own page, with the reference and the tracking link you already have.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add the carrier in Route, under Couriers, with your account reference and the services you buy.
2. Paste your own tracking URL with {reference} where the consignment number goes.
3. Record the service, the reference and the packages on each delivery, and attach the carrier's own label.

### More

- On the website: [Fortec](/integrations/fortec).

## CSV import and export

URL: https://kabaido.ai/docs/integrations/csv

Start from the spreadsheets you already have, and take your tables out again whenever you want them.

Import the catalogue from CSV or Excel and customers, suppliers and price lists from CSV; export tables as CSV.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Data in and out |
| For | Every workspace |

### What you get

Start from the spreadsheets you already have, and take your tables out again whenever you want them.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Upload the file and let the wizard sniff the delimiter and the header.
2. Map the columns onto your schema and fix what it flags.
3. Run the dry run and read the validation report before anything is written.
4. Export the filtered table as CSV or JSON from the areas that offer it.

### More

- The full guide: [csv import export reference](/docs/integrations/csv-import-export-reference).
- On the website: [CSV import and export](/integrations/csv).

## Custom outbound webhook

URL: https://kabaido.ai/docs/integrations/webhook-out

Your own system hears about every quote, order and service the moment it happens.

Send quote, order and service events to any URL as signed JSON.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Data in and out |
| For | Every workspace |

### What you get

Your own system hears about every quote, order and service the moment it happens.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an endpoint below with the https URL that should receive the events.
2. Choose the events to send, or leave it on everything.
3. Verify the X-Kabaido-Signature header on your side using the secret shown once at creation.

### More

- The full guide: [webhooks](/docs/api/webhooks).
- On the website: [Custom outbound webhook](/integrations/webhook-out).

## Custom inbound endpoint

URL: https://kabaido.ai/docs/integrations/inbound

Any system that can POST JSON can open a request or keep your customers and products up to date.

A tokenised URL any system can post JSON to: open a request, upsert customers or products, or move an order.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Data in and out |
| For | Every workspace |

### What you get

Any system that can POST JSON can open a request or keep your customers and products up to date.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an endpoint below and choose what a post to it should do.
2. Copy the tokenised URL and, if you want one, the signing secret.
3. Post JSON to it and watch the receipts under the endpoint.

### More

- The full guide: [inbound endpoints](/docs/api/inbound-endpoints).
- On the website: [Custom inbound endpoint](/integrations/inbound).

## Custom REST connection

URL: https://kabaido.ai/docs/integrations/rest

Customers are pulled from whatever system holds them, on a schedule, with the credential stored encrypted.

Pull products and customers on a schedule from any JSON API with bearer, basic or header auth.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Data in and out |
| For | Every workspace |

### What you get

Customers are pulled from whatever system holds them, on a schedule, with the credential stored encrypted.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Point the connection at the endpoint that lists your customers.
2. Map the company, email and reference fields, then test the fetch.
3. Schedule the daily sync or leave it on manual.

### More

- The full guide: [rest connections](/docs/catalog/rest-connections).
- On the website: [Custom REST connection](/integrations/rest).

## Kabaido API

URL: https://kabaido.ai/docs/integrations/api

Whatever you run internally reads the data your team works on and writes what the API allows, with a key you can revoke.

Read quotes, orders and stock, and write customers, requests, products and stock movements, over the REST API.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Build on Kabaido |
| For | Every workspace |

### What you get

Whatever you run internally reads the data your team works on and writes what the API allows, with a key you can revoke.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a key and copy it; the full key is shown once and never again.
2. Give it only the scopes the caller needs.
3. Call the API with an Authorization: Bearer header.

### More

- The full guide: [the rest api](/docs/api/the-rest-api).
- On the website: [Kabaido API](/integrations/api).

## Any team calendar

URL: https://kabaido.ai/docs/integrations/org-calendar

It would put a window you promised a customer in the diary of the person who has to keep it, and read their busy time back into the planner.

Not built yet. Delivery windows, site visits and collection slots written into your team's own calendar are on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Calendars |
| For | [Route](/docs/route), [Service Centre](/docs/service-centre) and [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. |
| What you hand over | Nothing to hand over yet. A connection would be an admin's sign in, scoped to calendar events only. |

### What you get

It would put a window you promised a customer in the diary of the person who has to keep it, and read their busy time back into the planner.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Any team calendar](/integrations/org-calendar).

## Invoice status from any package

URL: https://kabaido.ai/docs/integrations/accounting

The order says which invoice it became and whether it has been paid, without anybody typing it twice.

Tell your accounting package an order is ready to invoice, and read the invoice reference and the paid state back.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Accounting |
| For | [Sales Engineer](/docs/sales-engineer), [Service Centre](/docs/service-centre), [Commerce](/docs/commerce) and [Source](/docs/source) |
| What moves | Out: an order ready to invoice, as an event with its number, customer and currency. In: the invoice reference, amount, dates and paid state. |
| What you hand over | The endpoint's own token, and optionally a signing secret. Your accounting package's credentials stay with your accounting package. |

### What you get

The order says which invoice it became and whether it has been paid, without anybody typing it twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an inbound endpoint below and copy its tokenised URL.
2. Point Zapier, Make, n8n or your own middleware at it, from your accounting package.
3. Post the invoice reference, amount and dates back against the order number.
4. The order shows the reference, the due date and the paid state.

### More

- On the website: [Invoice status from any package](/integrations/accounting).

## Wizard embed

URL: https://kabaido.ai/docs/integrations/wizard-embed

Somebody on your website gets a specification they can act on, and you see what they asked.

Put a wizard on your own website, where every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | In: every run, with what it asked and what it answered. Out: nothing leaves the platform. |
| What you hand over | An embed key, which is scoped to your organisation and to the domains you name. |

### What you get

Somebody on your website gets a specification they can act on, and you see what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for an embed key, limited to the domains you name.
2. Add an iframe that points at the embed address for that key to the page where the wizard should run.
3. Every run appears in the wizard's activity in the Wizard area.

### More

- The full guide: [embedding a wizard](/docs/wizard/embedding-a-wizard).
- On the website: [Wizard embed](/integrations/wizard-embed).

## Commerce site connection

URL: https://kabaido.ai/docs/integrations/commerce-site

Orders, accounts and enquiries from your website land here with your numbering, your pricing and your VAT, and a content change publishes itself.

The link between a Kabaido built website and this workspace.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | In: website orders, registered accounts, enquiries and page events. Out: the revalidate push when content changes. |
| What you hand over | A site key minted with the build. Rotating it is a support conversation. |

### What you get

Orders, accounts and enquiries from your website land here with your numbering, your pricing and your VAT, and a content change publishes itself.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. The Kabaido team mints the site key when the site is built.
2. Orders, accounts, enquiries and page events arrive on it.
3. Publishing content from the Commerce area revalidates the live site.

### More

- The full guide: [the website build](/docs/commerce/the-website-build).
- On the website: [Commerce site connection](/integrations/commerce-site).

## Gmail and Google Workspace

URL: https://kabaido.ai/docs/integrations/gmail

Work where your customers already write to you. An enquiry becomes a request without anyone forwarding it, and the reply threads on the original message.

Connect a Gmail or Google Workspace inbox and the agent reads new mail, opens requests and drafts branded replies.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Messaging |
| For | [Sales Engineer](/docs/sales-engineer), [Design Engineer](/docs/design-engineer), [Route](/docs/route), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre), [Machinist](/docs/machinist), [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |
| What moves | In: new messages and their attachments, classified as a request for quotation, a purchase order, a technical question or none. Out: the drafted reply, sent from the connected address so it threads in the customer's mailbox. |
| What you hand over | A Google sign in on the inbox itself, scoped to reading mail and sending as that address. The token is held in a server only store and is never on a row a member can read. |

### What you get

Work where your customers already write to you. An enquiry becomes a request without anyone forwarding it, and the reply threads on the original message.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Connect the inbox here and approve the Google sign in.
2. Choose review mode or direct sending, and the address drafts go to.
3. Let the agent read from now on: it never backfills the mailbox.
4. Check the first few drafts, then decide whether to send directly.

### More

- On the website: [Gmail and Google Workspace](/integrations/gmail).

## Microsoft 365 and Outlook

URL: https://kabaido.ai/docs/integrations/microsoft

Work where your customers already write to you. An enquiry becomes a request without anyone forwarding it, and the reply threads on the original message.

Connect a Microsoft 365 or Outlook inbox and the agent reads new mail, opens requests and drafts branded replies.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Messaging |
| For | [Sales Engineer](/docs/sales-engineer), [Design Engineer](/docs/design-engineer), [Route](/docs/route), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre), [Machinist](/docs/machinist), [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |
| What moves | In: new messages and their attachments through Microsoft Graph, classified as a request for quotation, a purchase order, a technical question or none. Out: the drafted reply, sent from the connected address so it threads in the customer's mailbox. |
| What you hand over | A Microsoft sign in on the inbox itself, with delegated permissions to read mail and send as that address. The token is held in a server only store and is never on a row a member can read. |

### What you get

Work where your customers already write to you. An enquiry becomes a request without anyone forwarding it, and the reply threads on the original message.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Connect the inbox here and approve the Microsoft sign in.
2. Choose review mode or direct sending, and the address drafts go to.
3. Let the agent read from now on: it anchors on today and never backfills.
4. Check the first few drafts, then decide whether to send directly.

### More

- On the website: [Microsoft 365 and Outlook](/integrations/microsoft).

## WhatsApp Business

URL: https://kabaido.ai/docs/integrations/whatsapp-business

It would read an enquiry arriving on WhatsApp the way the email agent reads one arriving by mail, and let the reply go back on the same thread.

Not built yet. A WhatsApp Business connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Messaging |
| For | [Sales Engineer](/docs/sales-engineer) |
| What moves | Nothing moves yet. Requests arrive today by email, through the customer surface and on an inbound endpoint. |
| What you hand over | Nothing to hand over yet. A connection would run on your own WhatsApp Business account. |

### What you get

It would read an enquiry arriving on WhatsApp the way the email agent reads one arriving by mail, and let the reply go back on the same thread.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [WhatsApp Business](/integrations/whatsapp-business).

## Intercom

URL: https://kabaido.ai/docs/integrations/intercom

Get quotes, orders and enquiries into Intercom today, without waiting for a named connector, using the automation tool you already pay for.

Move Kabaido events into Intercom through Zapier, Make or n8n, and write back over the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Messaging |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the events you choose, as signed JSON. In: whatever your scenario writes back through the Kabaido API. Kabaido never talks to Intercom directly. |
| What you hand over | A Kabaido API key for the write back, plus your own Intercom credential inside the automation tool. Kabaido never holds your Intercom credential. |

### What you get

Get quotes, orders and enquiries into Intercom today, without waiting for a named connector, using the automation tool you already pay for.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here and choose the events to send.
2. Catch it in Zapier, Make or n8n with a webhook trigger.
3. Map the payload onto an Intercom action in that tool.
4. For the other direction, call the Kabaido API from the same scenario with an API key.

### More

- On the website: [Intercom](/integrations/intercom).

## Crisp

URL: https://kabaido.ai/docs/integrations/crisp

Get quotes, orders and enquiries into Crisp today, without waiting for a named connector, using the automation tool you already pay for.

Move Kabaido events into Crisp through Zapier, Make or n8n, and write back over the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Messaging |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the events you choose, as signed JSON. In: whatever your scenario writes back through the Kabaido API. Kabaido never talks to Crisp directly. |
| What you hand over | A Kabaido API key for the write back, plus your own Crisp credential inside the automation tool. Kabaido never holds your Crisp credential. |

### What you get

Get quotes, orders and enquiries into Crisp today, without waiting for a named connector, using the automation tool you already pay for.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here and choose the events to send.
2. Catch it in Zapier, Make or n8n with a webhook trigger.
3. Map the payload onto a Crisp action in that tool.
4. For the other direction, call the Kabaido API from the same scenario with an API key.

### More

- On the website: [Crisp](/integrations/crisp).

## Aircall

URL: https://kabaido.ai/docs/integrations/aircall

It would log the call against the company in Inspect and put what was said into the debrief, so a phone conversation compounded the same way a visit does.

Not built yet. An Aircall connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Messaging |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect records a debrief against the company by hand today, and that debrief folds into the profile. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Aircall account. |

### What you get

It would log the call against the company in Inspect and put what was said into the debrief, so a phone conversation compounded the same way a visit does.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Aircall](/integrations/aircall).

## Google Calendar

URL: https://kabaido.ai/docs/integrations/google-calendar

It would put the windows you promise customers into the diary of the person who has to keep them.

Not built for your own calendar yet. Writing delivery windows, visits and collection slots into your Google Calendar is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Calendars |
| For | [Sales Engineer](/docs/sales-engineer), [Design Engineer](/docs/design-engineer), [Route](/docs/route), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre), [Machinist](/docs/machinist), [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |
| What moves | Nothing moves to your calendar yet. Calls booked with the Kabaido team run on Kabaido's own scheduling calendar, not yours. |
| What you hand over | Nothing to hand over yet. A connection would be an admin's Google sign in, scoped to calendar events. |

### What you get

It would put the windows you promise customers into the diary of the person who has to keep them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- The full guide: [scheduling](/docs/integrations/scheduling).
- On the website: [Google Calendar](/integrations/google-calendar).

## Google Meet

URL: https://kabaido.ai/docs/integrations/google-meet

It would add a Google Meet link to the meetings your own team books through Kabaido.

Not built for your own meetings yet. Only calls booked with the Kabaido team carry a Google Meet link.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Calendars |
| For | [Sales Engineer](/docs/sales-engineer) |
| What moves | Nothing moves yet. The Meet links that exist are created on Kabaido's own scheduling account. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would add a Google Meet link to the meetings your own team books through Kabaido.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- The full guide: [scheduling](/docs/integrations/scheduling).
- On the website: [Google Meet](/integrations/google-meet).

## Microsoft 365 Calendar

URL: https://kabaido.ai/docs/integrations/microsoft-calendar

It would let your own users connect their work calendar, so delivery windows, site visits and collection slots were written as events and their busy time was respected.

Not built yet. Reading and writing a Microsoft 365 calendar is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Calendars |
| For | [Sales Engineer](/docs/sales-engineer) and [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Kabaido books its own meetings on Google Calendar today, and every date in the platform exports as an ordinary calendar file. |
| What you hand over | Nothing to hand over yet. A connection would be a Microsoft sign in scoped to calendar events only. |

### What you get

It would let your own users connect their work calendar, so delivery windows, site visits and collection slots were written as events and their busy time was respected.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Microsoft 365 Calendar](/integrations/microsoft-calendar).

## Google Maps Platform

URL: https://kabaido.ai/docs/integrations/google-maps

It would sequence a day of stops and hold a promised window against real drive times rather than against an estimate.

Not built yet. A Google Maps Platform connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Data in and out |
| For | [Route](/docs/route) and [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Runs carry their stops in the order you set today, and each address holds its own coordinates. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Google Cloud key. |

### What you get

It would sequence a day of stops and hold a promised window against real drive times rather than against an estimate.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Maps Platform](/integrations/google-maps).

## what3words

URL: https://kabaido.ai/docs/integrations/what3words

It would let a driver or a site visitor record exactly where a delivery or a survey happened on a site with no useful street address.

Not built yet. A what3words connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Data in and out |
| For | [Route](/docs/route) and [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. A delivery records its address, its proof of delivery and its scan events today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own what3words key. |

### What you get

It would let a driver or a site visitor record exactly where a delivery or a survey happened on a site with no useful street address.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [what3words](/integrations/what3words).

## Akeneo

URL: https://kabaido.ai/docs/integrations/akeneo

Let Akeneo stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

Bring your product records out of Akeneo into the Kabaido catalogue on a scheduled pull or as a file.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Data in and out |
| For | [Wizard](/docs/wizard) and [Commerce](/docs/commerce) |
| What moves | In: products, their attributes and their media references, on the schedule you set or when you import the file. Out: nothing. Kabaido does not write back into Akeneo. |
| What you hand over | A read credential from your own Akeneo account, or simply the exported file. Kabaido holds a credential encrypted and never shows it again. |

### What you get

Let Akeneo stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Export or expose the channel you want from Akeneo, as an API endpoint or a file.
2. Create the catalogue connection here with that endpoint and your own credential, or start a file import.
3. Map the fields onto your schema, run the dry run and read the validation report.
4. Schedule the pull, then re run it whenever the schema changes.

### More

- On the website: [Akeneo](/integrations/akeneo).

## Pimberly

URL: https://kabaido.ai/docs/integrations/pimberly

Let Pimberly stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

Bring your product records out of Pimberly into the Kabaido catalogue on a scheduled pull or as a file.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Data in and out |
| For | [Wizard](/docs/wizard) and [Commerce](/docs/commerce) |
| What moves | In: products, their attributes and their media references, on the schedule you set or when you import the file. Out: nothing. Kabaido does not write back into Pimberly. |
| What you hand over | A read credential from your own Pimberly account, or simply the exported file. Kabaido holds a credential encrypted and never shows it again. |

### What you get

Let Pimberly stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Export or expose the channel you want from Pimberly, as an API endpoint or a file.
2. Create the catalogue connection here with that endpoint and your own credential, or start a file import.
3. Map the fields onto your schema, run the dry run and read the validation report.
4. Schedule the pull, then re run it whenever the schema changes.

### More

- On the website: [Pimberly](/integrations/pimberly).

## Plytix

URL: https://kabaido.ai/docs/integrations/plytix

Let Plytix stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

Bring your product records out of Plytix into the Kabaido catalogue on a scheduled pull or as a file.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Data in and out |
| For | [Wizard](/docs/wizard) |
| What moves | In: products, their attributes and their media references, on the schedule you set or when you import the file. Out: nothing. Kabaido does not write back into Plytix. |
| What you hand over | A read credential from your own Plytix account, or simply the exported file. Kabaido holds a credential encrypted and never shows it again. |

### What you get

Let Plytix stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Export or expose the channel you want from Plytix, as an API endpoint or a file.
2. Create the catalogue connection here with that endpoint and your own credential, or start a file import.
3. Map the fields onto your schema, run the dry run and read the validation report.
4. Schedule the pull, then re run it whenever the schema changes.

### More

- On the website: [Plytix](/integrations/plytix).

## Epicor Kinetic

URL: https://kabaido.ai/docs/integrations/epicor

Quote against the customer accounts Epicor Kinetic already holds, rather than a copy somebody retyped.

Pull customers from Epicor Kinetic on a scheduled REST connection, and let Epicor Kinetic post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |
| What moves | In: customers on the schedule you set, and order status when Epicor Kinetic posts it. Out: quote and order events as signed JSON for your own middleware. Kabaido never writes into Epicor Kinetic itself. |
| What you hand over | An endpoint URL and a credential from your own Epicor Kinetic account: a bearer token, basic auth or a header key. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the customer accounts Epicor Kinetic already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in Epicor Kinetic as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so Epicor Kinetic can post progress back.

### More

- On the website: [Epicor Kinetic](/integrations/epicor).

## Sage X3

URL: https://kabaido.ai/docs/integrations/sage-x3

Quote against the customer accounts Sage X3 already holds, rather than a copy somebody retyped.

Pull customers from Sage X3 on a scheduled REST connection, and let Sage X3 post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | Every workspace |
| What moves | In: customers on the schedule you set, and order status when Sage X3 posts it. Out: quote and order events as signed JSON for your own middleware. Kabaido never writes into Sage X3 itself. |
| What you hand over | An endpoint URL and a credential from your own Sage X3 account: a bearer token, basic auth or a header key. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the customer accounts Sage X3 already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in Sage X3 as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so Sage X3 can post progress back.

### More

- On the website: [Sage X3](/integrations/sage-x3).

## Infor CloudSuite Industrial (SyteLine)

URL: https://kabaido.ai/docs/integrations/infor-syteline

Quote against the customer accounts Infor CloudSuite Industrial (SyteLine) already holds, rather than a copy somebody retyped.

Pull customers from Infor CloudSuite Industrial (SyteLine) on a scheduled REST connection, and let Infor CloudSuite Industrial (SyteLine) post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer) and [Source](/docs/source) |
| What moves | In: customers on the schedule you set, and order status when Infor CloudSuite Industrial (SyteLine) posts it. Out: quote and order events as signed JSON for your own middleware. Kabaido never writes into Infor CloudSuite Industrial (SyteLine) itself. |
| What you hand over | An endpoint URL and a credential from your own Infor CloudSuite Industrial (SyteLine) account: a bearer token, basic auth or a header key. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the customer accounts Infor CloudSuite Industrial (SyteLine) already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in Infor CloudSuite Industrial (SyteLine) as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so Infor CloudSuite Industrial (SyteLine) can post progress back.

### More

- On the website: [Infor CloudSuite Industrial (SyteLine)](/integrations/infor-syteline).

## 123insight (Forterro)

URL: https://kabaido.ai/docs/integrations/123insight

Quote against the customer accounts 123insight (Forterro) already holds, rather than a copy somebody retyped.

Pull customers from 123insight (Forterro) on a scheduled REST connection, and let 123insight (Forterro) post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |
| What moves | In: customers on the schedule you set, and order status when 123insight (Forterro) posts it. Out: quote and order events as signed JSON for your own middleware. Kabaido never writes into 123insight (Forterro) itself. |
| What you hand over | An endpoint URL and a credential from your own 123insight (Forterro) account: a bearer token, basic auth or a header key. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the customer accounts 123insight (Forterro) already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in 123insight (Forterro) as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so 123insight (Forterro) can post progress back.

### More

- On the website: [123insight (Forterro)](/integrations/123insight).

## OrderWise

URL: https://kabaido.ai/docs/integrations/orderwise

Quote against the customer accounts OrderWise already holds, rather than a copy somebody retyped.

Pull customers from OrderWise on a scheduled REST connection, and let OrderWise post order status back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |
| What moves | In: customers on the schedule you set, and order status when OrderWise posts it. Out: quote and order events as signed JSON for your own middleware. Kabaido never writes into OrderWise itself. |
| What you hand over | An endpoint URL and a credential from your own OrderWise account: a bearer token, basic auth or a header key. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the customer accounts OrderWise already holds, rather than a copy somebody retyped.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Expose the customer list in OrderWise as one JSON response from its API.
2. Create a REST connection here with that endpoint and your own credential.
3. Map the company, email and reference fields, then run the test fetch.
4. Add an inbound endpoint with the ERP order status action so OrderWise can post progress back.

### More

- On the website: [OrderWise](/integrations/orderwise).

## Unleashed

URL: https://kabaido.ai/docs/integrations/unleashed

Let Unleashed keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Unleashed into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source) and [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Unleashed stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Unleashed needs inside the automation tool. Kabaido holds no Unleashed credential. |

### What you get

Let Unleashed keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Unleashed.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Unleashed](/integrations/unleashed).

## Cin7 Core

URL: https://kabaido.ai/docs/integrations/cin7-core

Let Cin7 Core keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Cin7 Core into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Source](/docs/source) and [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Cin7 Core stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Cin7 Core needs inside the automation tool. Kabaido holds no Cin7 Core credential. |

### What you get

Let Cin7 Core keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Cin7 Core.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Cin7 Core](/integrations/cin7-core).

## Katana

URL: https://kabaido.ai/docs/integrations/katana

Let Katana keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Katana into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Katana stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Katana needs inside the automation tool. Kabaido holds no Katana credential. |

### What you get

Let Katana keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Katana.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Katana](/integrations/katana).

## MRPeasy

URL: https://kabaido.ai/docs/integrations/mrpeasy

Let MRPeasy keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from MRPeasy into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. MRPeasy stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever MRPeasy needs inside the automation tool. Kabaido holds no MRPeasy credential. |

### What you get

Let MRPeasy keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in MRPeasy.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [MRPeasy](/integrations/mrpeasy).

## Fishbowl

URL: https://kabaido.ai/docs/integrations/fishbowl

Let Fishbowl keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Fishbowl into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Fishbowl stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Fishbowl needs inside the automation tool. Kabaido holds no Fishbowl credential. |

### What you get

Let Fishbowl keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Fishbowl.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Fishbowl](/integrations/fishbowl).

## Linnworks

URL: https://kabaido.ai/docs/integrations/linnworks

Let Linnworks keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Linnworks into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Linnworks stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Linnworks needs inside the automation tool. Kabaido holds no Linnworks credential. |

### What you get

Let Linnworks keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Linnworks.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Linnworks](/integrations/linnworks).

## Brightpearl

URL: https://kabaido.ai/docs/integrations/brightpearl

Let Brightpearl keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Brightpearl into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Brightpearl stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Brightpearl needs inside the automation tool. Kabaido holds no Brightpearl credential. |

### What you get

Let Brightpearl keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Brightpearl.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Brightpearl](/integrations/brightpearl).

## Descartes Peoplevox

URL: https://kabaido.ai/docs/integrations/peoplevox

Let Descartes Peoplevox keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

Post stock movements from Descartes Peoplevox into the Kabaido ledger through Zapier, Make or n8n and the stock API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | ERP |
| For | [Stock](/docs/stock) |
| What moves | In: movements posted through the stock API, each with its reason. Out: nothing, because Kabaido sends no stock events yet. Descartes Peoplevox stays the owner of what it owns. |
| What you hand over | A Kabaido API key for your automation, and whatever Descartes Peoplevox needs inside the automation tool. Kabaido holds no Descartes Peoplevox credential. |

### What you get

Let Descartes Peoplevox keep owning the quantities it owns, with each movement recorded in the Kabaido ledger instead of typed twice.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create a Kabaido API key with the stock write scope.
2. In Zapier, Make or n8n, trigger on a movement or a balance change in Descartes Peoplevox.
3. Post it to the Kabaido stock movements endpoint as an adjustment with its reason.
4. Check the first movements in the Stock ledger before you rely on it.

### More

- On the website: [Descartes Peoplevox](/integrations/peoplevox).

## Sage 200

URL: https://kabaido.ai/docs/integrations/sage200

Stop the retyping between the order and the invoice. Sage 200 stays the system of record and Kabaido records the reference.

Send order events to Sage 200 through Zapier, Make or n8n, and record the invoice reference it raises.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Sales Engineer](/docs/sales-engineer), [Source](/docs/source), [Stock](/docs/stock), [Service Centre](/docs/service-centre) and [Commerce](/docs/commerce) |
| What moves | Out: quote and order events as signed JSON, including an order ready to invoice. In: the invoice reference, dates and paid state on the order invoice action. Kabaido never calls Sage 200 itself. |
| What you hand over | Whatever Sage 200 needs inside your automation tool. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Stop the retyping between the order and the invoice. Sage 200 stays the system of record and Kabaido records the reference.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here for the order events, pointed at your Zapier, Make or n8n hook.
2. In the automation, raise the invoice in Sage 200 from the payload.
3. Add an inbound endpoint with the order invoice action.
4. Have the automation post the invoice reference and the paid state back, and the order shows them.

### More

- On the website: [Sage 200](/integrations/sage200).

## Dext

URL: https://kabaido.ai/docs/integrations/dext

Match what a supplier billed against what you ordered, without anyone typing the invoice into two systems.

Pass supplier invoices from Dext into Kabaido through Zapier, Make or n8n, against the purchase order.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Source](/docs/source) |
| What moves | In: supplier invoices on the supplier invoice action. Out: nothing to Dext. Kabaido never calls Dext itself. |
| What you hand over | Whatever Dext needs inside your automation tool. Kabaido's side is a tokenised inbound URL, created here. |

### What you get

Match what a supplier billed against what you ordered, without anyone typing the invoice into two systems.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an inbound endpoint here with the supplier invoice action.
2. In Zapier, Make or n8n, trigger on a new supplier bill in Dext.
3. Post the supplier, the purchase order number and the invoice details to the endpoint.
4. Check the first invoice lands against its purchase order.

### More

- On the website: [Dext](/integrations/dext).

## Lightyear

URL: https://kabaido.ai/docs/integrations/lightyear

Match what a supplier billed against what you ordered, without anyone typing the invoice into two systems.

Pass supplier invoices from Lightyear into Kabaido through Zapier, Make or n8n, against the purchase order.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | Accounting |
| For | [Source](/docs/source) |
| What moves | In: supplier invoices on the supplier invoice action. Out: nothing to Lightyear. Kabaido never calls Lightyear itself. |
| What you hand over | Whatever Lightyear needs inside your automation tool. Kabaido's side is a tokenised inbound URL, created here. |

### What you get

Match what a supplier billed against what you ordered, without anyone typing the invoice into two systems.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an inbound endpoint here with the supplier invoice action.
2. In Zapier, Make or n8n, trigger on a new supplier bill in Lightyear.
3. Post the supplier, the purchase order number and the invoice details to the endpoint.
4. Check the first invoice lands against its purchase order.

### More

- On the website: [Lightyear](/integrations/lightyear).

## Stripe

URL: https://kabaido.ai/docs/integrations/stripe

It would let a customer pay a Commerce order or settle an account through your own Stripe account.

Not built for your own payments. Kabaido bills its own subscriptions through Stripe; taking your customers' payments is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Sales Engineer](/docs/sales-engineer) and [Commerce](/docs/commerce) |
| What moves | Kabaido code talks to Stripe for Kabaido's own subscriptions, not for an organisation's payments. Nothing about your customers, your orders or your invoices is sent to Stripe, and a payment your customer makes to you does not pass through Kabaido. |
| What you hand over | Nothing from you. Kabaido's billing runs on Kabaido's own Stripe account. Your own Stripe account is not connected to anything. |

### What you get

It would let a customer pay a Commerce order or settle an account through your own Stripe account.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Stripe](/integrations/stripe).

## GoCardless

URL: https://kabaido.ai/docs/integrations/gocardless

It would let a customer pay a Commerce order or settle an account through GoCardless, with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through GoCardless is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Sales Engineer](/docs/sales-engineer) and [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own GoCardless account. |

### What you get

It would let a customer pay a Commerce order or settle an account through GoCardless, with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [GoCardless](/integrations/gocardless).

## PayPal

URL: https://kabaido.ai/docs/integrations/paypal

It would let a customer pay a Commerce order or settle an account through PayPal, with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through PayPal is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own PayPal account. |

### What you get

It would let a customer pay a Commerce order or settle an account through PayPal, with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [PayPal](/integrations/paypal).

## Opayo by Elavon

URL: https://kabaido.ai/docs/integrations/opayo

It would let a customer pay a Commerce order or settle an account through Opayo by Elavon, with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through Opayo by Elavon is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Opayo by Elavon account. |

### What you get

It would let a customer pay a Commerce order or settle an account through Opayo by Elavon, with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Opayo by Elavon](/integrations/opayo).

## Wise Business

URL: https://kabaido.ai/docs/integrations/wise-business

It would let a customer pay a Commerce order or settle an account through Wise Business, with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through Wise Business is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Wise Business account. |

### What you get

It would let a customer pay a Commerce order or settle an account through Wise Business, with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Wise Business](/integrations/wise-business).

## Modulr

URL: https://kabaido.ai/docs/integrations/modulr

It would let a customer pay a Commerce order or settle an account through Modulr, with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through Modulr is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Modulr account. |

### What you get

It would let a customer pay a Commerce order or settle an account through Modulr, with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Modulr](/integrations/modulr).

## Open banking feeds (TrueLayer, Plaid)

URL: https://kabaido.ai/docs/integrations/open-banking

It would let a customer pay a Commerce order or settle an account through Open banking feeds (TrueLayer, Plaid), with the payment recorded against the order rather than reconciled later.

Not built yet. Taking payment through Open banking feeds (TrueLayer, Plaid) is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Payments |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. Commerce orders carry your terms and your account today, and payment is taken the way you already take it. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Open banking feeds (TrueLayer, Plaid) account. |

### What you get

It would let a customer pay a Commerce order or settle an account through Open banking feeds (TrueLayer, Plaid), with the payment recorded against the order rather than reconciled later.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Open banking feeds (TrueLayer, Plaid)](/integrations/open-banking).

## Pipedrive

URL: https://kabaido.ai/docs/integrations/pipedrive

Quote against the accounts your sales team already keeps, and let Pipedrive see what happened to the enquiry without anyone copying it across.

Pull companies from Pipedrive into Customers on a schedule, and push quote and order events back out.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | CRM |
| For | [Sales Engineer](/docs/sales-engineer), [Wizard](/docs/wizard) and [Inspect](/docs/inspect) |
| What moves | In: companies and their identifying fields, on the schedule you set. Out: quote and order events as signed JSON, which your automation maps onto Pipedrive records. |
| What you hand over | A read credential from your own Pipedrive account. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the accounts your sales team already keeps, and let Pipedrive see what happened to the enquiry without anyone copying it across.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an API credential in Pipedrive with read access to companies.
2. Create a REST connection here with the companies endpoint and that credential.
3. Map the company name, the domain and your own account reference, then test the fetch.
4. Schedule the pull, then add an outbound endpoint for the events you want back in.

### More

- On the website: [Pipedrive](/integrations/pipedrive).

## Zoho CRM

URL: https://kabaido.ai/docs/integrations/zoho-crm

Quote against the accounts your sales team already keeps, and let Zoho CRM see what happened to the enquiry without anyone copying it across.

Pull companies from Zoho CRM into Customers on a schedule, and push quote and order events back out.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | CRM |
| For | [Sales Engineer](/docs/sales-engineer), [Wizard](/docs/wizard) and [Inspect](/docs/inspect) |
| What moves | In: companies and their identifying fields, on the schedule you set. Out: quote and order events as signed JSON, which your automation maps onto Zoho CRM records. |
| What you hand over | A read credential from your own Zoho CRM account. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the accounts your sales team already keeps, and let Zoho CRM see what happened to the enquiry without anyone copying it across.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an API credential in Zoho CRM with read access to companies.
2. Create a REST connection here with the companies endpoint and that credential.
3. Map the company name, the domain and your own account reference, then test the fetch.
4. Schedule the pull, then add an outbound endpoint for the events you want back in.

### More

- On the website: [Zoho CRM](/integrations/zoho-crm).

## Microsoft Dynamics 365 Sales

URL: https://kabaido.ai/docs/integrations/dynamics365-sales

Quote against the accounts your sales team already keeps, and let Microsoft Dynamics 365 Sales see what happened to the enquiry without anyone copying it across.

Pull companies from Microsoft Dynamics 365 Sales into Customers on a schedule, and push quote and order events back out.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | CRM |
| For | [Sales Engineer](/docs/sales-engineer) and [Inspect](/docs/inspect) |
| What moves | In: companies and their identifying fields, on the schedule you set. Out: quote and order events as signed JSON, which your automation maps onto Microsoft Dynamics 365 Sales records. |
| What you hand over | A read credential from your own Microsoft Dynamics 365 Sales account. Kabaido holds it encrypted and never shows it again. |

### What you get

Quote against the accounts your sales team already keeps, and let Microsoft Dynamics 365 Sales see what happened to the enquiry without anyone copying it across.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Create an API credential in Microsoft Dynamics 365 Sales with read access to companies.
2. Create a REST connection here with the companies endpoint and that credential.
3. Map the company name, the domain and your own account reference, then test the fetch.
4. Schedule the pull, then add an outbound endpoint for the events you want back in.

### More

- On the website: [Microsoft Dynamics 365 Sales](/integrations/dynamics365-sales).

## Mailchimp

URL: https://kabaido.ai/docs/integrations/mailchimp

Get quotes, orders and enquiries into Mailchimp today, without waiting for a named connector, using the automation tool you already pay for.

Move Kabaido events into Mailchimp through Zapier, Make or n8n, and write back over the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | CRM |
| For | [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |
| What moves | Out: the events you choose, as signed JSON. In: whatever your scenario writes back through the Kabaido API. Kabaido never talks to Mailchimp directly. |
| What you hand over | A Kabaido API key for the write back, plus your own Mailchimp credential inside the automation tool. Kabaido never holds your Mailchimp credential. |

### What you get

Get quotes, orders and enquiries into Mailchimp today, without waiting for a named connector, using the automation tool you already pay for.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here and choose the events to send.
2. Catch it in Zapier, Make or n8n with a webhook trigger.
3. Map the payload onto a Mailchimp action in that tool.
4. For the other direction, call the Kabaido API from the same scenario with an API key.

### More

- On the website: [Mailchimp](/integrations/mailchimp).

## Brevo

URL: https://kabaido.ai/docs/integrations/brevo

Get quotes, orders and enquiries into Brevo today, without waiting for a named connector, using the automation tool you already pay for.

Move Kabaido events into Brevo through Zapier, Make or n8n, and write back over the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | CRM |
| For | [Wizard](/docs/wizard), [Inspect](/docs/inspect) and [Commerce](/docs/commerce) |
| What moves | Out: the events you choose, as signed JSON. In: whatever your scenario writes back through the Kabaido API. Kabaido never talks to Brevo directly. |
| What you hand over | A Kabaido API key for the write back, plus your own Brevo credential inside the automation tool. Kabaido never holds your Brevo credential. |

### What you get

Get quotes, orders and enquiries into Brevo today, without waiting for a named connector, using the automation tool you already pay for.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here and choose the events to send.
2. Catch it in Zapier, Make or n8n with a webhook trigger.
3. Map the payload onto a Brevo action in that tool.
4. For the other direction, call the Kabaido API from the same scenario with an API key.

### More

- On the website: [Brevo](/integrations/brevo).

## Klaviyo

URL: https://kabaido.ai/docs/integrations/klaviyo

Get quotes, orders and enquiries into Klaviyo today, without waiting for a named connector, using the automation tool you already pay for.

Move Kabaido events into Klaviyo through Zapier, Make or n8n, and write back over the Kabaido API.

|  |  |
| --- | --- |
| Status | **Via automation**: Through Zapier, Make or n8n. |
| Kind | CRM |
| For | [Wizard](/docs/wizard) and [Commerce](/docs/commerce) |
| What moves | Out: the events you choose, as signed JSON. In: whatever your scenario writes back through the Kabaido API. Kabaido never talks to Klaviyo directly. |
| What you hand over | A Kabaido API key for the write back, plus your own Klaviyo credential inside the automation tool. Kabaido never holds your Klaviyo credential. |

### What you get

Get quotes, orders and enquiries into Klaviyo today, without waiting for a named connector, using the automation tool you already pay for.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add an outbound endpoint here and choose the events to send.
2. Catch it in Zapier, Make or n8n with a webhook trigger.
3. Map the payload onto a Klaviyo action in that tool.
4. For the other direction, call the Kabaido API from the same scenario with an API key.

### More

- On the website: [Klaviyo](/integrations/klaviyo).

## Companies House API

URL: https://kabaido.ai/docs/integrations/companies-house

Ground every profile in the public register, so a name, a status or an overdue filing is a fact with a source rather than an assumption.

Inspect reads the Companies House register for the company's own filings and refreshes what changed.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | In: the company profile, the register status and the charges, refreshed on a weekly pass and cited on the profile. Out: nothing. Kabaido never writes to the register. |
| What you hand over | Nothing from you. Kabaido reads the public register on its own key, within the rate the register allows. |

### What you get

Ground every profile in the public register, so a name, a status or an overdue filing is a fact with a source rather than an assumption.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Nothing to connect: Inspect reads the public register on Kabaido's own key.
2. Open any mapped company and read its register facts with their source.
3. Watch for the signals a filing raises, such as a dissolution or overdue accounts.
4. Ask for a county to be mapped if yours is not live yet.

### More

- On the website: [Companies House API](/integrations/companies-house).

## Creditsafe

URL: https://kabaido.ai/docs/integrations/creditsafe

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

Not built yet. A Creditsafe connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect builds its profiles from public sources and cites every data point. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Creditsafe subscription. |

### What you get

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Creditsafe](/integrations/creditsafe).

## Endole

URL: https://kabaido.ai/docs/integrations/endole

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

Not built yet. A Endole connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect builds its profiles from public sources and cites every data point. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Endole subscription. |

### What you get

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Endole](/integrations/endole).

## Experian Business

URL: https://kabaido.ai/docs/integrations/experian-business

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

Not built yet. A Experian Business connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect builds its profiles from public sources and cites every data point. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Experian Business subscription. |

### What you get

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Experian Business](/integrations/experian-business).

## Dun and Bradstreet

URL: https://kabaido.ai/docs/integrations/dun-bradstreet

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

Not built yet. A Dun and Bradstreet connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect builds its profiles from public sources and cites every data point. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Dun and Bradstreet subscription. |

### What you get

It would put a financial standing and firmographic view beside the Inspect profile, so the commercial risk sat next to the engineering evidence before anyone got in the car.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Dun and Bradstreet](/integrations/dun-bradstreet).

## Cognism

URL: https://kabaido.ai/docs/integrations/cognism

It would find and reveal contacts at a mapped company from your own Cognism account, charged to your own account and never to a Kabaido pool.

Not built yet. A Cognism connector is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect finds contacts today through the connectors that are built, and contacts import as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Cognism account. |

### What you get

It would find and reveal contacts at a mapped company from your own Cognism account, charged to your own account and never to a Kabaido pool.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Cognism](/integrations/cognism).

## Lusha

URL: https://kabaido.ai/docs/integrations/lusha

It would find and reveal contacts at a mapped company from your own Lusha account, charged to your own account and never to a Kabaido pool.

Not built yet. A Lusha connector is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect finds contacts today through the connectors that are built, and contacts import as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Lusha account. |

### What you get

It would find and reveal contacts at a mapped company from your own Lusha account, charged to your own account and never to a Kabaido pool.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Lusha](/integrations/lusha).

## LinkedIn Sales Navigator

URL: https://kabaido.ai/docs/integrations/linkedin-sales-navigator

It would find and reveal contacts at a mapped company from your own LinkedIn Sales Navigator account, charged to your own account and never to a Kabaido pool.

Not built yet. A LinkedIn Sales Navigator connector is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect finds contacts today through the connectors that are built, and contacts import as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own LinkedIn Sales Navigator account. |

### What you get

It would find and reveal contacts at a mapped company from your own LinkedIn Sales Navigator account, charged to your own account and never to a Kabaido pool.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [LinkedIn Sales Navigator](/integrations/linkedin-sales-navigator).

## Smartlead

URL: https://kabaido.ai/docs/integrations/smartlead

It would push an Inspect list into a Smartlead sequence and read the replies back onto the company, so the outreach and the profile stayed one record.

Not built yet. A Smartlead connector is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect sends through your own connected inbox today, which keeps the sending reputation yours. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Smartlead account. |

### What you get

It would push an Inspect list into a Smartlead sequence and read the replies back onto the company, so the outreach and the profile stayed one record.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Smartlead](/integrations/smartlead).

## Instantly

URL: https://kabaido.ai/docs/integrations/instantly

It would push an Inspect list into an Instantly sequence and read the replies back onto the company, so the outreach and the profile stayed one record.

Not built yet. A Instantly connector is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Contact finders |
| For | [Inspect](/docs/inspect) |
| What moves | Nothing moves yet. Inspect sends through your own connected inbox today, which keeps the sending reputation yours. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Instantly account. |

### What you get

It would push an Inspect list into an Instantly sequence and read the replies back onto the company, so the outreach and the profile stayed one record.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Instantly](/integrations/instantly).

## Shiptheory

URL: https://kabaido.ai/docs/integrations/shiptheory

It would let Shiptheory book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Shiptheory and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Today a consignment booked in Shiptheory is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Shiptheory account. |

### What you get

It would let Shiptheory book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Shiptheory](/integrations/shiptheory).

## Metapack

URL: https://kabaido.ai/docs/integrations/metapack

It would let Metapack book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Metapack and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. Today a consignment booked in Metapack is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Metapack account. |

### What you get

It would let Metapack book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Metapack](/integrations/metapack).

## Sorted

URL: https://kabaido.ai/docs/integrations/sorted

It would let Sorted book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Sorted and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. Today a consignment booked in Sorted is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Sorted account. |

### What you get

It would let Sorted book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Sorted](/integrations/sorted).

## ShipStation

URL: https://kabaido.ai/docs/integrations/shipstation

It would let ShipStation book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to ShipStation and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. Today a consignment booked in ShipStation is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own ShipStation account. |

### What you get

It would let ShipStation book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ShipStation](/integrations/shipstation).

## Despatch Cloud

URL: https://kabaido.ai/docs/integrations/despatch-cloud

It would let Despatch Cloud book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Despatch Cloud and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. Today a consignment booked in Despatch Cloud is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Despatch Cloud account. |

### What you get

It would let Despatch Cloud book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Despatch Cloud](/integrations/despatch-cloud).

## Shipmate

URL: https://kabaido.ai/docs/integrations/shipmate

It would let Shipmate book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Shipmate and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. Today a consignment booked in Shipmate is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Shipmate account. |

### What you get

It would let Shipmate book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Shipmate](/integrations/shipmate).

## Mintsoft

URL: https://kabaido.ai/docs/integrations/mintsoft

It would let Mintsoft book the carrier and return the label and the tracking onto the Kabaido delivery.

Not built yet. Handing consignments to Mintsoft and reading the label and tracking back is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) and [Stock](/docs/stock) |
| What moves | Nothing moves yet. Today a consignment booked in Mintsoft is recorded on the delivery by hand, with its reference and tracking link. |
| What you hand over | Nothing to hand over yet. A connection would use an API credential from your own Mintsoft account. |

### What you get

It would let Mintsoft book the carrier and return the label and the tracking onto the Kabaido delivery.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Mintsoft](/integrations/mintsoft).

## Samsara

URL: https://kabaido.ai/docs/integrations/samsara

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

Not built yet. A Samsara connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. The driver's own station screen records each stop, the signature and the time today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Samsara account. |

### What you get

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Samsara](/integrations/samsara).

## Webfleet

URL: https://kabaido.ai/docs/integrations/webfleet

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

Not built yet. A Webfleet connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. The driver's own station screen records each stop, the signature and the time today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Webfleet account. |

### What you get

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Webfleet](/integrations/webfleet).

## Quartix

URL: https://kabaido.ai/docs/integrations/quartix

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

Not built yet. A Quartix connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. The driver's own station screen records each stop, the signature and the time today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Quartix account. |

### What you get

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Quartix](/integrations/quartix).

## Verizon Connect

URL: https://kabaido.ai/docs/integrations/verizon-connect

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

Not built yet. A Verizon Connect connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Delivery, carriers and vehicles |
| For | [Route](/docs/route) |
| What moves | Nothing moves yet. The driver's own station screen records each stop, the signature and the time today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Verizon Connect account. |

### What you get

It would put the vehicle's real position and its driving time onto the run, so the promised window moved with the van rather than with an estimate.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Verizon Connect](/integrations/verizon-connect).

## Zebra

URL: https://kabaido.ai/docs/integrations/zebra

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through Zebra and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Route](/docs/route) and [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to Zebra. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to Zebra. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install Zebra's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [Zebra](/integrations/zebra).

## Brother

URL: https://kabaido.ai/docs/integrations/brother

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through Brother and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Route](/docs/route) and [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to Brother. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to Brother. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install Brother's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [Brother](/integrations/brother).

## BarTender

URL: https://kabaido.ai/docs/integrations/bartender

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through BarTender and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Route](/docs/route) and [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to BarTender. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to BarTender. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install BarTender's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [BarTender](/integrations/bartender).

## NiceLabel

URL: https://kabaido.ai/docs/integrations/nicelabel

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through NiceLabel and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Route](/docs/route) and [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to NiceLabel. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to NiceLabel. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install NiceLabel's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [NiceLabel](/integrations/nicelabel).

## Honeywell

URL: https://kabaido.ai/docs/integrations/honeywell

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through Honeywell and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to Honeywell. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to Honeywell. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install Honeywell's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [Honeywell](/integrations/honeywell).

## Datalogic

URL: https://kabaido.ai/docs/integrations/datalogic

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

Print Kabaido's label PDFs through Datalogic and scan the codes back in at any station.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Stock](/docs/stock) |
| What moves | Out: the label PDF, exactly as Kabaido renders it. In: the scanned code, as keyboard input. No vendor API is involved and nothing is sent to Datalogic. |
| What you hand over | Nothing. The printer and the scanner are yours and Kabaido never signs in to Datalogic. |

### What you get

Use the hardware you already own. Kabaido's labels are ordinary PDFs and its scan stations read keyboard input, so nothing is locked to one vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Install Datalogic's own driver or label software on the machine that prints.
2. Print a Kabaido label PDF to it once and set the media size.
3. Open the scan station on that machine and scan a code into the field.
4. Set the scanner's suffix to a carriage return so each scan submits on its own.

### More

- On the website: [Datalogic](/integrations/datalogic).

## Any USB or Bluetooth wedge scanner

URL: https://kabaido.ai/docs/integrations/wedge-scanner

Use the scanners you already own and buy more from anyone. Nothing in Kabaido is tied to a scanner vendor.

Any USB or Bluetooth wedge scanner works at a scan station, because a scan is keyboard input.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Scanners, labels and printers |
| For | [Stock](/docs/stock) |
| What moves | In: the scanned code, as keyboard input, which becomes a movement, a station handover or a lookup. Out: nothing. No driver and no vendor API are involved. |
| What you hand over | Nothing. The scanner is yours and Kabaido never talks to it directly. |

### What you get

Use the scanners you already own and buy more from anyone. Nothing in Kabaido is tied to a scanner vendor.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Pair or plug in the scanner on the machine that will use it.
2. Set its suffix to a carriage return so each scan submits on its own.
3. Open the scan station and scan a code into the field.
4. Check the movement it wrote, then leave the station open on that machine.

### More

- On the website: [Any USB or Bluetooth wedge scanner](/integrations/wedge-scanner).

## CribMaster

URL: https://kabaido.ai/docs/integrations/cribmaster

It would take each vend as a consumption movement, so the crib and the stock ledger told the same story without a stocktake to reconcile them.

Not built yet. A CribMaster connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Scanners, labels and printers |
| For | [Stock](/docs/stock) |
| What moves | Nothing moves yet. Consumption is recorded at the machine, at the bench or on a count today, and every movement carries its reason, its person and its time. |
| What you hand over | Nothing to hand over yet. A connection would run on your own CribMaster installation. |

### What you get

It would take each vend as a consumption movement, so the crib and the stock ledger told the same story without a stocktake to reconcile them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [CribMaster](/integrations/cribmaster).

## SupplyPro

URL: https://kabaido.ai/docs/integrations/supplypro

It would take each vend as a consumption movement, so the vending units and the stock ledger told the same story without a stocktake to reconcile them.

Not built yet. A SupplyPro connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Scanners, labels and printers |
| For | [Stock](/docs/stock) |
| What moves | Nothing moves yet. Consumption is recorded at the machine, at the bench or on a count today, and every movement carries its reason, its person and its time. |
| What you hand over | Nothing to hand over yet. A connection would run on your own SupplyPro account. |

### What you get

It would take each vend as a consumption movement, so the vending units and the stock ledger told the same story without a stocktake to reconcile them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SupplyPro](/integrations/supplypro).

## EDI (EDIFACT, ANSI X12, AS2)

URL: https://kabaido.ai/docs/integrations/edi

Trade with a customer or a supplier who mandates EDI without running a second purchasing system beside Kabaido.

Send purchase orders out and take acknowledgements and invoices back through your own EDI translator.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON. In: acknowledgements and supplier invoices. Kabaido does not speak EDIFACT, ANSI X12 or AS2 on the wire: your translator sits between and does that part. |
| What you hand over | Whatever your translator and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates EDI without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message versions with the trading party.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [EDI (EDIFACT, ANSI X12, AS2)](/integrations/edi).

## cXML and OCI punchout

URL: https://kabaido.ai/docs/integrations/cxml-oci-punchout

It would let a buyer whose procurement system mandates punchout shop your catalogue and return the basket as an order.

Not built yet. Punchout from a buyer's procurement system into a Kabaido order is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. A procurement system can post to an inbound endpoint today, which opens a request, not an order. |
| What you hand over | Nothing to hand over yet. A connection would use the identities and secrets the buyer's procurement system issues. |

### What you get

It would let a buyer whose procurement system mandates punchout shop your catalogue and return the basket as an order.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [cXML and OCI punchout](/integrations/cxml-oci-punchout).

## SAP Ariba

URL: https://kabaido.ai/docs/integrations/sap-ariba

Trade with a customer or a supplier who mandates SAP Ariba without running a second purchasing system beside Kabaido.

Send purchase orders out to SAP Ariba and take acknowledgements and invoices back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between. |
| What you hand over | Whatever SAP Ariba and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates SAP Ariba without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message shape with whoever mandates SAP Ariba.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [SAP Ariba](/integrations/sap-ariba).

## Coupa

URL: https://kabaido.ai/docs/integrations/coupa

Trade with a customer or a supplier who mandates Coupa without running a second purchasing system beside Kabaido.

Send purchase orders out to Coupa and take acknowledgements and invoices back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between. |
| What you hand over | Whatever Coupa and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates Coupa without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message shape with whoever mandates Coupa.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [Coupa](/integrations/coupa).

## Jaggaer

URL: https://kabaido.ai/docs/integrations/jaggaer

Trade with a customer or a supplier who mandates Jaggaer without running a second purchasing system beside Kabaido.

Send purchase orders out to Jaggaer and take acknowledgements and invoices back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between. |
| What you hand over | Whatever Jaggaer and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates Jaggaer without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message shape with whoever mandates Jaggaer.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [Jaggaer](/integrations/jaggaer).

## Proactis

URL: https://kabaido.ai/docs/integrations/proactis

Trade with a customer or a supplier who mandates Proactis without running a second purchasing system beside Kabaido.

Send purchase orders out to Proactis and take acknowledgements and invoices back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between. |
| What you hand over | Whatever Proactis and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates Proactis without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message shape with whoever mandates Proactis.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [Proactis](/integrations/proactis).

## Basware

URL: https://kabaido.ai/docs/integrations/basware

Trade with a customer or a supplier who mandates Basware without running a second purchasing system beside Kabaido.

Send purchase orders out to Basware and take acknowledgements and invoices back.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between. |
| What you hand over | Whatever Basware and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here. |

### What you get

Trade with a customer or a supplier who mandates Basware without running a second purchasing system beside Kabaido.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Agree the document set and the message shape with whoever mandates Basware.
2. Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
3. Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
4. Run one live document each way and check the order moves with it.

### More

- On the website: [Basware](/integrations/basware).

## Supplier price files

URL: https://kabaido.ai/docs/integrations/supplier-price-files

Price from what you actually pay today, from the supplier's own file rather than a retyped copy.

Import a supplier's price list into Source from a CSV file, as a draft list you check before use.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | In: supplier codes and unit prices from a CSV file. Excel and PDF files, and capture from the email agent, are not built. Out: nothing. |
| What you hand over | Nothing beyond the file itself. |

### What you get

Price from what you actually pay today, from the supplier's own file rather than a retyped copy.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. In Suppliers, open the price lists and choose to import one.
2. Pick the supplier, name the list and set its currency and the dates it is valid for.
3. Upload the CSV: it needs a unit price column and a supplier SKU or SKU column.
4. Check the draft list before you put it to use.

### More

- The full guide: [price lists](/docs/source/price-lists).
- On the website: [Supplier price files](/integrations/supplier-price-files).

## TraceParts

URL: https://kabaido.ai/docs/integrations/traceparts

It would pull a supplier's own model and datasheet onto a catalogue record, so a bought in part carried its real geometry rather than a description.

Not built yet. A TraceParts connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. Catalogue records take models, drawings and datasheets as uploaded files today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own TraceParts account. |

### What you get

It would pull a supplier's own model and datasheet onto a catalogue record, so a bought in part carried its real geometry rather than a description.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [TraceParts](/integrations/traceparts).

## CADENAS PARTsolutions

URL: https://kabaido.ai/docs/integrations/cadenas-partsolutions

It would pull a supplier's own model and datasheet onto a catalogue record, so a bought in part carried its real geometry rather than a description.

Not built yet. A CADENAS PARTsolutions connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Supplier networks and EDI |
| For | [Source](/docs/source) |
| What moves | Nothing moves yet. Catalogue records take models, drawings and datasheets as uploaded files today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own CADENAS account. |

### What you get

It would pull a supplier's own model and datasheet onto a catalogue record, so a bought in part carried its real geometry rather than a description.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [CADENAS PARTsolutions](/integrations/cadenas-partsolutions).

## MTConnect

URL: https://kabaido.ai/docs/integrations/mtconnect

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data over MTConnect is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine and a controller to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [MTConnect](/integrations/mtconnect).

## OPC UA

URL: https://kabaido.ai/docs/integrations/opc-ua

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data over OPC UA is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine and a controller to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [OPC UA](/integrations/opc-ua).

## MQTT

URL: https://kabaido.ai/docs/integrations/mqtt

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data over MQTT is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine and a controller to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [MQTT](/integrations/mqtt).

## FANUC FOCAS

URL: https://kabaido.ai/docs/integrations/fanuc-focas

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data over FANUC FOCAS is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine and a controller to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [FANUC FOCAS](/integrations/fanuc-focas).

## Modbus TCP

URL: https://kabaido.ai/docs/integrations/modbus-tcp

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data over Modbus TCP is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine and a controller to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Modbus TCP](/integrations/modbus-tcp).

## Siemens SINUMERIK and Insights Hub

URL: https://kabaido.ai/docs/integrations/sinumerik

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Siemens SINUMERIK and Insights Hub is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Siemens SINUMERIK and Insights Hub](/integrations/sinumerik).

## Heidenhain StateMonitor

URL: https://kabaido.ai/docs/integrations/statemonitor

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Heidenhain StateMonitor is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Heidenhain StateMonitor](/integrations/statemonitor).

## Haas MyHaas

URL: https://kabaido.ai/docs/integrations/myhaas

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Haas MyHaas is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Haas MyHaas](/integrations/myhaas).

## Mazak SMOOTH and SmartBox

URL: https://kabaido.ai/docs/integrations/mazak-smooth

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Mazak SMOOTH and SmartBox is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Mazak SMOOTH and SmartBox](/integrations/mazak-smooth).

## Okuma Connect Plan

URL: https://kabaido.ai/docs/integrations/okuma-connect-plan

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Okuma Connect Plan is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Okuma Connect Plan](/integrations/okuma-connect-plan).

## DN Solutions

URL: https://kabaido.ai/docs/integrations/dn-solutions

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from DN Solutions is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [DN Solutions](/integrations/dn-solutions).

## Fanuc MT-LINKi

URL: https://kabaido.ai/docs/integrations/mt-linki

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Fanuc MT-LINKi is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Fanuc MT-LINKi](/integrations/mt-linki).

## Fronius WeldCube

URL: https://kabaido.ai/docs/integrations/weldcube

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Fronius WeldCube is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Fronius WeldCube](/integrations/weldcube).

## Lincoln Electric CheckPoint

URL: https://kabaido.ai/docs/integrations/lincoln-checkpoint

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Lincoln Electric CheckPoint is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Lincoln Electric CheckPoint](/integrations/lincoln-checkpoint).

## ESAB WeldCloud

URL: https://kabaido.ai/docs/integrations/esab-weldcloud

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from ESAB WeldCloud is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ESAB WeldCloud](/integrations/esab-weldcloud).

## Miller Insight

URL: https://kabaido.ai/docs/integrations/miller-insight

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

Not built yet. Reading live machine data from Miller Insight is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would put the machine's own state, counts and alarms onto the job, so run time, downtime and pieces came from the machine rather than from somebody typing them.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Miller Insight](/integrations/miller-insight).

## MachineMetrics

URL: https://kabaido.ai/docs/integrations/machinemetrics

It would take the machine state and the counts MachineMetrics already collects and put them onto the Kabaido job, rather than collecting the same data twice.

Not built yet. A MachineMetrics connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A connection would run on your own MachineMetrics account. |

### What you get

It would take the machine state and the counts MachineMetrics already collects and put them onto the Kabaido job, rather than collecting the same data twice.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [MachineMetrics](/integrations/machinemetrics).

## Tulip

URL: https://kabaido.ai/docs/integrations/tulip

It would let a Tulip app at the station write its step completions onto the Kabaido job, so one floor did not run two sets of screens.

Not built yet. A Tulip connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects run time, piece counts and material at the station screen today, recorded by the operator as the job moves. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Tulip account. |

### What you get

It would let a Tulip app at the station write its step completions onto the Kabaido job, so one floor did not run two sets of screens.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Tulip](/integrations/tulip).

## Time and attendance (Mitrefinch, Kelio)

URL: https://kabaido.ai/docs/integrations/time-attendance

It would reconcile the minutes a job collected at the machine against the hours the workforce system recorded, so labour cost and payroll agreed.

Not built yet. A time and attendance connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Machinist collects the minutes between scans against the job today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own account. |

### What you get

It would reconcile the minutes a job collected at the machine against the hours the workforce system recorded, so labour cost and payroll agreed.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Time and attendance (Mitrefinch, Kelio)](/integrations/time-attendance).

## ZOLLER TMS Tool Management Solutions

URL: https://kabaido.ai/docs/integrations/zoller-tms

It would read the tool's own identity, geometry and life from ZOLLER TMS Tool Management Solutions and carry it onto the service job, so the item arriving and the record already held were the same thing.

Not built yet. A ZOLLER TMS Tool Management Solutions connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre registers each item with its own traced code today, and item data imports as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own ZOLLER TMS Tool Management Solutions licences. |

### What you get

It would read the tool's own identity, geometry and life from ZOLLER TMS Tool Management Solutions and carry it onto the service job, so the item arriving and the record already held were the same thing.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ZOLLER TMS Tool Management Solutions](/integrations/zoller-tms).

## ZOLLER presetters

URL: https://kabaido.ai/docs/integrations/zoller-presetters

It would read the tool's own identity, geometry and life from ZOLLER presetters and carry it onto the service job, so the item arriving and the record already held were the same thing.

Not built yet. A ZOLLER presetters connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre registers each item with its own traced code today, and item data imports as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own ZOLLER presetters licences. |

### What you get

It would read the tool's own identity, geometry and life from ZOLLER presetters and carry it onto the service job, so the item arriving and the record already held were the same thing.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ZOLLER presetters](/integrations/zoller-presetters).

## TDM Systems

URL: https://kabaido.ai/docs/integrations/tdm-systems

It would read the tool's own identity, geometry and life from TDM Systems and carry it onto the service job, so the item arriving and the record already held were the same thing.

Not built yet. A TDM Systems connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre registers each item with its own traced code today, and item data imports as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own TDM Systems licences. |

### What you get

It would read the tool's own identity, geometry and life from TDM Systems and carry it onto the service job, so the item arriving and the record already held were the same thing.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [TDM Systems](/integrations/tdm-systems).

## Sandvik CoroPlus Tool Library

URL: https://kabaido.ai/docs/integrations/sandvik-coroplus

It would read the tool's own identity, geometry and life from Sandvik CoroPlus Tool Library and carry it onto the service job, so the item arriving and the record already held were the same thing.

Not built yet. A Sandvik CoroPlus Tool Library connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre registers each item with its own traced code today, and item data imports as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Sandvik CoroPlus Tool Library licences. |

### What you get

It would read the tool's own identity, geometry and life from Sandvik CoroPlus Tool Library and carry it onto the service job, so the item arriving and the record already held were the same thing.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Sandvik CoroPlus Tool Library](/integrations/sandvik-coroplus).

## ANCA (ToolRoom, iView)

URL: https://kabaido.ai/docs/integrations/anca

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off ANCA (ToolRoom, iView) grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ANCA (ToolRoom, iView)](/integrations/anca).

## WALTER HELITRONIC TOOL STUDIO

URL: https://kabaido.ai/docs/integrations/walter-helitronic

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off WALTER HELITRONIC TOOL STUDIO grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [WALTER HELITRONIC TOOL STUDIO](/integrations/walter-helitronic).

## NUMROTO

URL: https://kabaido.ai/docs/integrations/numroto

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off NUMROTO grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [NUMROTO](/integrations/numroto).

## VOLLMER

URL: https://kabaido.ai/docs/integrations/vollmer

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off VOLLMER grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [VOLLMER](/integrations/vollmer).

## Rollomatic

URL: https://kabaido.ai/docs/integrations/rollomatic

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off Rollomatic grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Rollomatic](/integrations/rollomatic).

## Schneeberger

URL: https://kabaido.ai/docs/integrations/schneeberger

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

Not built yet. Reading job data off Schneeberger grinding machines is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Machines and the shop floor |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and the minutes between scans become the job's real cost. |
| What you hand over | Nothing to hand over yet. A real connection needs a machine to prove it against. |

### What you get

It would take the grinding programme, the wheel life and the finished result off the machine and onto the service job, so the record matched what the machine actually did.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Schneeberger](/integrations/schneeberger).

## Mitutoyo MeasurLink

URL: https://kabaido.ai/docs/integrations/mitutoyo-measurlink

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Mitutoyo MeasurLink connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Mitutoyo MeasurLink licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Mitutoyo MeasurLink](/integrations/mitutoyo-measurlink).

## ZEISS CALYPSO

URL: https://kabaido.ai/docs/integrations/zeiss-calypso

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A ZEISS CALYPSO connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own ZEISS CALYPSO licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [ZEISS CALYPSO](/integrations/zeiss-calypso).

## Hexagon PC-DMIS

URL: https://kabaido.ai/docs/integrations/hexagon-pcdmis

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Hexagon PC-DMIS connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Hexagon PC-DMIS licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Hexagon PC-DMIS](/integrations/hexagon-pcdmis).

## Renishaw Equator

URL: https://kabaido.ai/docs/integrations/renishaw-equator

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Renishaw Equator connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Renishaw Equator licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Renishaw Equator](/integrations/renishaw-equator).

## Marposs

URL: https://kabaido.ai/docs/integrations/marposs

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Marposs connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Marposs licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Marposs](/integrations/marposs).

## Ideagen Quality Management (Q-Pulse)

URL: https://kabaido.ai/docs/integrations/ideagen-qpulse

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Ideagen Quality Management (Q-Pulse) connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Ideagen Quality Management (Q-Pulse) licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Ideagen Quality Management (Q-Pulse)](/integrations/ideagen-qpulse).

## Qualsys

URL: https://kabaido.ai/docs/integrations/qualsys

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Qualsys connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Qualsys licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Qualsys](/integrations/qualsys).

## Intelex

URL: https://kabaido.ai/docs/integrations/intelex

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A Intelex connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Intelex licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Intelex](/integrations/intelex).

## IndySoft

URL: https://kabaido.ai/docs/integrations/indysoft

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A IndySoft connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own IndySoft licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [IndySoft](/integrations/indysoft).

## GAGEtrak

URL: https://kabaido.ai/docs/integrations/gagetrak

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

Not built yet. A GAGEtrak connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. Service Centre records every station handover as a scan event today, and those records export as CSV. |
| What you hand over | Nothing to hand over yet. A connection would run on your own GAGEtrak licences. |

### What you get

It would pull the measured results and the instrument state onto the service job, so the record came from the measuring system rather than from a spreadsheet.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [GAGEtrak](/integrations/gagetrak).

## UKAS certificate records

URL: https://kabaido.ai/docs/integrations/ukas-certificates

It would attach the certificate a calibration laboratory issued to the item and the service job, so the paperwork and the work were one record. Kabaido issues no certificate and holds no accreditation of its own.

Not built yet. Holding a calibration certificate against the item it belongs to is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Quality, measurement and calibration |
| For | [Service Centre](/docs/service-centre) |
| What moves | Nothing moves yet. A certificate uploads as an attachment on the service item today, and every station handover is already a scan event with a person and a time behind it. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would attach the certificate a calibration laboratory issued to the item and the service job, so the paperwork and the work were one record. Kabaido issues no certificate and holds no accreditation of its own.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [UKAS certificate records](/integrations/ukas-certificates).

## SOLIDWORKS

URL: https://kabaido.ai/docs/integrations/solidworks

It would open a configured design in SOLIDWORKS, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct SOLIDWORKS connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which SOLIDWORKS opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own SOLIDWORKS licences. |

### What you get

It would open a configured design in SOLIDWORKS, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SOLIDWORKS](/integrations/solidworks).

## Autodesk Inventor

URL: https://kabaido.ai/docs/integrations/inventor

It would open a configured design in Autodesk Inventor, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Autodesk Inventor connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Autodesk Inventor opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Autodesk Inventor licences. |

### What you get

It would open a configured design in Autodesk Inventor, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Autodesk Inventor](/integrations/inventor).

## Autodesk Fusion

URL: https://kabaido.ai/docs/integrations/fusion

It would open a configured design in Autodesk Fusion, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Autodesk Fusion connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Autodesk Fusion opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Autodesk Fusion licences. |

### What you get

It would open a configured design in Autodesk Fusion, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Autodesk Fusion](/integrations/fusion).

## AutoCAD

URL: https://kabaido.ai/docs/integrations/autocad

It would open a configured design in AutoCAD, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct AutoCAD connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which AutoCAD opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own AutoCAD licences. |

### What you get

It would open a configured design in AutoCAD, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [AutoCAD](/integrations/autocad).

## Solid Edge

URL: https://kabaido.ai/docs/integrations/solid-edge

It would open a configured design in Solid Edge, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Solid Edge connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Solid Edge opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Solid Edge licences. |

### What you get

It would open a configured design in Solid Edge, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Solid Edge](/integrations/solid-edge).

## Siemens NX

URL: https://kabaido.ai/docs/integrations/siemens-nx

It would open a configured design in Siemens NX, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Siemens NX connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Siemens NX opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Siemens NX licences. |

### What you get

It would open a configured design in Siemens NX, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Siemens NX](/integrations/siemens-nx).

## PTC Creo

URL: https://kabaido.ai/docs/integrations/ptc-creo

It would open a configured design in PTC Creo, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct PTC Creo connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which PTC Creo opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own PTC Creo licences. |

### What you get

It would open a configured design in PTC Creo, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [PTC Creo](/integrations/ptc-creo).

## Onshape

URL: https://kabaido.ai/docs/integrations/onshape

It would open a configured design in Onshape, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Onshape connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Onshape opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Onshape licences. |

### What you get

It would open a configured design in Onshape, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Onshape](/integrations/onshape).

## Rhino

URL: https://kabaido.ai/docs/integrations/rhino

It would open a configured design in Rhino, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct Rhino connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which Rhino opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Rhino licences. |

### What you get

It would open a configured design in Rhino, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Rhino](/integrations/rhino).

## FreeCAD

URL: https://kabaido.ai/docs/integrations/freecad

It would open a configured design in FreeCAD, or take a model from it, without anyone exporting a file by hand.

Not built yet. A direct FreeCAD connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, which FreeCAD opens. |
| What you hand over | Nothing to hand over yet. A connection would run on your own FreeCAD licences. |

### What you get

It would open a configured design in FreeCAD, or take a model from it, without anyone exporting a file by hand.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [FreeCAD](/integrations/freecad).

## STEP

URL: https://kabaido.ai/docs/integrations/step

Hand a real solid to whoever needs it, so a customer, a programmer or a supplier starts from the geometry rather than from a picture of it.

Every configured design exports as a STEP solid.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Out: the solid, written by the same kernel that built the preview, so the file and the picture are the same shape. In: reading a STEP file you were sent is not built. |
| What you hand over | Nothing. The geometry is built in your own browser and the file is yours. |

### What you get

Hand a real solid to whoever needs it, so a customer, a programmer or a supplier starts from the geometry rather than from a picture of it.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Configure the design until the rules pass.
2. Choose STEP on the export and the kernel writes it from the same model the viewer shows.
3. Attach it to the quote, or download it for your own systems.

### More

- On the website: [STEP](/integrations/step).

## STL

URL: https://kabaido.ai/docs/integrations/stl

Get a printable or viewable mesh straight out of the configured design, without a conversion step somewhere else.

Every configured design exports as an STL mesh, ready for printing or for a mesh workflow.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Out: the mesh, at the tolerance the viewer used. In: nothing in Design Engineer. Machinist reads an uploaded STL for its size, volume and area. |
| What you hand over | Nothing. The geometry is built in your own browser and the file is yours. |

### What you get

Get a printable or viewable mesh straight out of the configured design, without a conversion step somewhere else.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Configure the design until the rules pass.
2. Choose STL on the export.
3. The mesh is written in your browser from the same model the viewer shows.
4. Attach it to the quote, or download it.

### More

- On the website: [STL](/integrations/stl).

## DXF

URL: https://kabaido.ai/docs/integrations/dxf

Send a cutting profile straight to whoever cuts it, with the loops separated so nesting and cutting do not need the file tidied first.

A design with a two dimensional profile exports as a DXF, with outer loops and cutouts on their own layers.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Out: the profile as a layered DXF. In: an attached DXF, measured for its profile or nested by the plasma machine module. |
| What you hand over | Nothing. The file is written from your own configuration and it is yours. |

### What you get

Send a cutting profile straight to whoever cuts it, with the loops separated so nesting and cutting do not need the file tidied first.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Configure a design that has a two dimensional profile.
2. Choose DXF on the export.
3. Outer loops are written on one layer and cutouts on another.
4. Attach it to the quote, or hand it to your cutting software.

### More

- On the website: [DXF](/integrations/dxf).

## PDF drawings

URL: https://kabaido.ai/docs/integrations/pdf-drawings

Give the customer something to approve and the workshop something to work from, generated from the same configuration as the price.

Every configured design exports a dimensioned specification sheet as a PDF.

|  |  |
| --- | --- |
| Status | **Works today**: Kabaido code talks to the provider. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Out: the specification sheet as a PDF, rendered from the live configuration. In: a PDF drawing attached to an enquiry is read by the request pipeline for what it can evidence. |
| What you hand over | Nothing. The sheet is rendered from your own configuration. |

### What you get

Give the customer something to approve and the workshop something to work from, generated from the same configuration as the price.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Configure the design until the rules pass.
2. Choose PDF on the export.
3. The sheet is rendered with the parameters, the views and your own branding.
4. Attach it to the quote or send it on its own.

### More

- On the website: [PDF drawings](/integrations/pdf-drawings).

## IGES

URL: https://kabaido.ai/docs/integrations/iges

It would let a design go out in IGES for the systems that ask for it, instead of being converted somewhere else first.

Not built yet. Reading or writing IGES is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and most systems that ask for IGES will take one of those. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would let a design go out in IGES for the systems that ask for it, instead of being converted somewhere else first.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [IGES](/integrations/iges).

## DWG

URL: https://kabaido.ai/docs/integrations/dwg

It would let a design go out in DWG for the systems that ask for it, instead of being converted somewhere else first.

Not built yet. Reading or writing DWG is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and most systems that ask for DWG will take one of those. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would let a design go out in DWG for the systems that ask for it, instead of being converted somewhere else first.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [DWG](/integrations/dwg).

## Parasolid (x_t)

URL: https://kabaido.ai/docs/integrations/parasolid

It would let a design go out in Parasolid (x_t) for the systems that ask for it, instead of being converted somewhere else first.

Not built yet. Reading or writing Parasolid (x_t) is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and most systems that ask for Parasolid (x_t) will take one of those. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would let a design go out in Parasolid (x_t) for the systems that ask for it, instead of being converted somewhere else first.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Parasolid (x_t)](/integrations/parasolid).

## SOLIDWORKS PDM

URL: https://kabaido.ai/docs/integrations/solidworks-pdm

It would check the model, the drawing and the production files of a configured design into SOLIDWORKS PDM under its own revision, so the vault stayed the single place a released file lives.

Not built yet. A SOLIDWORKS PDM link is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Every configured design's files download from Kabaido today and check in by hand. |
| What you hand over | Nothing to hand over yet. A connection would run on your own SOLIDWORKS PDM licences. |

### What you get

It would check the model, the drawing and the production files of a configured design into SOLIDWORKS PDM under its own revision, so the vault stayed the single place a released file lives.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SOLIDWORKS PDM](/integrations/solidworks-pdm).

## Autodesk Vault

URL: https://kabaido.ai/docs/integrations/autodesk-vault

It would check the model, the drawing and the production files of a configured design into Autodesk Vault under its own revision, so the vault stayed the single place a released file lives.

Not built yet. A Autodesk Vault link is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Every configured design's files download from Kabaido today and check in by hand. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Autodesk Vault licences. |

### What you get

It would check the model, the drawing and the production files of a configured design into Autodesk Vault under its own revision, so the vault stayed the single place a released file lives.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Autodesk Vault](/integrations/autodesk-vault).

## Autodesk Fusion Manage

URL: https://kabaido.ai/docs/integrations/fusion-manage

It would check the model, the drawing and the production files of a configured design into Autodesk Fusion Manage under its own revision, so the vault stayed the single place a released file lives.

Not built yet. A Autodesk Fusion Manage link is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Every configured design's files download from Kabaido today and check in by hand. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Autodesk Fusion Manage licences. |

### What you get

It would check the model, the drawing and the production files of a configured design into Autodesk Fusion Manage under its own revision, so the vault stayed the single place a released file lives.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Autodesk Fusion Manage](/integrations/fusion-manage).

## Arena PLM

URL: https://kabaido.ai/docs/integrations/arena-plm

It would check the model, the drawing and the production files of a configured design into Arena PLM under its own revision, so the vault stayed the single place a released file lives.

Not built yet. A Arena PLM link is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Every configured design's files download from Kabaido today and check in by hand. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Arena PLM licences. |

### What you get

It would check the model, the drawing and the production files of a configured design into Arena PLM under its own revision, so the vault stayed the single place a released file lives.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Arena PLM](/integrations/arena-plm).

## Mastercam

URL: https://kabaido.ai/docs/integrations/mastercam

It would pass the configured geometry and its cutting data straight to Mastercam, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Mastercam hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Mastercam takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Mastercam licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Mastercam, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Mastercam](/integrations/mastercam).

## Autodesk Fusion CAM

URL: https://kabaido.ai/docs/integrations/fusion-cam

It would pass the configured geometry and its cutting data straight to Autodesk Fusion CAM, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Autodesk Fusion CAM hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Autodesk Fusion CAM takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Autodesk Fusion CAM licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Autodesk Fusion CAM, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Autodesk Fusion CAM](/integrations/fusion-cam).

## Edgecam (Hexagon)

URL: https://kabaido.ai/docs/integrations/edgecam

It would pass the configured geometry and its cutting data straight to Edgecam (Hexagon), so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Edgecam (Hexagon) hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Edgecam (Hexagon) takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Edgecam (Hexagon) licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Edgecam (Hexagon), so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Edgecam (Hexagon)](/integrations/edgecam).

## Alphacam (Hexagon)

URL: https://kabaido.ai/docs/integrations/alphacam

It would pass the configured geometry and its cutting data straight to Alphacam (Hexagon), so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Alphacam (Hexagon) hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Alphacam (Hexagon) takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Alphacam (Hexagon) licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Alphacam (Hexagon), so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Alphacam (Hexagon)](/integrations/alphacam).

## Radan (Hexagon)

URL: https://kabaido.ai/docs/integrations/radan

It would pass the configured geometry and its cutting data straight to Radan (Hexagon), so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Radan (Hexagon) hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Radan (Hexagon) takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Radan (Hexagon) licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Radan (Hexagon), so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Radan (Hexagon)](/integrations/radan).

## SolidCAM

URL: https://kabaido.ai/docs/integrations/solidcam

It would pass the configured geometry and its cutting data straight to SolidCAM, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct SolidCAM hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which SolidCAM takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own SolidCAM licences. |

### What you get

It would pass the configured geometry and its cutting data straight to SolidCAM, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SolidCAM](/integrations/solidcam).

## hyperMILL

URL: https://kabaido.ai/docs/integrations/hypermill

It would pass the configured geometry and its cutting data straight to hyperMILL, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct hyperMILL hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which hyperMILL takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own hyperMILL licences. |

### What you get

It would pass the configured geometry and its cutting data straight to hyperMILL, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [hyperMILL](/integrations/hypermill).

## Lantek

URL: https://kabaido.ai/docs/integrations/lantek

It would pass the configured geometry and its cutting data straight to Lantek, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Lantek hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Lantek takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Lantek licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Lantek, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Lantek](/integrations/lantek).

## SigmaNEST

URL: https://kabaido.ai/docs/integrations/sigmanest

It would pass the configured geometry and its cutting data straight to SigmaNEST, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct SigmaNEST hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Design Engineer](/docs/design-engineer) and [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which SigmaNEST takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own SigmaNEST licences. |

### What you get

It would pass the configured geometry and its cutting data straight to SigmaNEST, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SigmaNEST](/integrations/sigmanest).

## Hypertherm ProNest

URL: https://kabaido.ai/docs/integrations/pronest

It would pass the configured geometry and its cutting data straight to Hypertherm ProNest, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Hypertherm ProNest hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Hypertherm ProNest takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Hypertherm ProNest licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Hypertherm ProNest, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Hypertherm ProNest](/integrations/pronest).

## TRUMPF TruTops

URL: https://kabaido.ai/docs/integrations/trutops

It would pass the configured geometry and its cutting data straight to TRUMPF TruTops, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct TRUMPF TruTops hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which TRUMPF TruTops takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own TRUMPF TruTops licences. |

### What you get

It would pass the configured geometry and its cutting data straight to TRUMPF TruTops, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [TRUMPF TruTops](/integrations/trutops).

## Bystronic

URL: https://kabaido.ai/docs/integrations/bystronic

It would pass the configured geometry and its cutting data straight to Bystronic, so the programmer started from the design rather than from a file somebody found.

Not built yet. A direct Bystronic hand off is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | CAD, CAM and file formats |
| For | [Machinist](/docs/machinist) |
| What moves | Nothing moves yet. Design Engineer writes STEP, STL, DXF and PDF today, and the cutting list exports as CSV, all of which Bystronic takes. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Bystronic licences. |

### What you get

It would pass the configured geometry and its cutting data straight to Bystronic, so the programmer started from the design rather than from a file somebody found.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Bystronic](/integrations/bystronic).

## WordPress

URL: https://kabaido.ai/docs/integrations/wordpress

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a WordPress page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves WordPress. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in WordPress. Kabaido never signs in to WordPress. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In WordPress, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [WordPress](/integrations/wordpress).

## Webflow

URL: https://kabaido.ai/docs/integrations/webflow

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a Webflow page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Webflow. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Webflow. Kabaido never signs in to Webflow. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Webflow, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Webflow](/integrations/webflow).

## Shopify

URL: https://kabaido.ai/docs/integrations/shopify

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a Shopify page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Shopify. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Shopify. Kabaido never signs in to Shopify. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Shopify, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Shopify](/integrations/shopify).

## WooCommerce

URL: https://kabaido.ai/docs/integrations/woocommerce

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a WooCommerce page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves WooCommerce. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in WooCommerce. Kabaido never signs in to WooCommerce. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In WooCommerce, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [WooCommerce](/integrations/woocommerce).

## Adobe Commerce (Magento)

URL: https://kabaido.ai/docs/integrations/adobe-commerce

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into an Adobe Commerce (Magento) page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Adobe Commerce (Magento). |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Adobe Commerce (Magento). Kabaido never signs in to Adobe Commerce (Magento). |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Adobe Commerce (Magento), add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Adobe Commerce (Magento)](/integrations/adobe-commerce).

## BigCommerce

URL: https://kabaido.ai/docs/integrations/bigcommerce

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a BigCommerce page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves BigCommerce. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in BigCommerce. Kabaido never signs in to BigCommerce. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In BigCommerce, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [BigCommerce](/integrations/bigcommerce).

## Wix

URL: https://kabaido.ai/docs/integrations/wix

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a Wix page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Wix. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Wix. Kabaido never signs in to Wix. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Wix, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Wix](/integrations/wix).

## Squarespace

URL: https://kabaido.ai/docs/integrations/squarespace

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a Squarespace page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Squarespace. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Squarespace. Kabaido never signs in to Squarespace. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Squarespace, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Squarespace](/integrations/squarespace).

## HubSpot CMS

URL: https://kabaido.ai/docs/integrations/hubspot-cms

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a HubSpot CMS page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves HubSpot CMS. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in HubSpot CMS. Kabaido never signs in to HubSpot CMS. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In HubSpot CMS, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [HubSpot CMS](/integrations/hubspot-cms).

## Drupal

URL: https://kabaido.ai/docs/integrations/drupal

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

Paste the Wizard embed into a Drupal page and every run shows in the wizard's activity.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Wizard](/docs/wizard) |
| What moves | Out: the wizard page, served from Kabaido in a frame. In: each run and its answers, in the wizard's activity. Nothing else leaves Drupal. |
| What you hand over | A Wizard embed key from the Kabaido team, limited to the domains you name, plus the right to edit a page in Drupal. Kabaido never signs in to Drupal. |

### What you get

Put an application engineer on your own website. A visitor answers what they know, gets a specification and your products against it, and the run lands in Kabaido with what they asked.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Ask the Kabaido team for a Wizard embed key for your domain.
2. In Drupal, add a custom HTML or embed block to the page you want.
3. Paste an iframe that points at the embed address for your key, publish the page and run the wizard once.
4. Check the run shows in the wizard's activity, then set who is notified.

### More

- On the website: [Drupal](/integrations/drupal).

## Cloudflare

URL: https://kabaido.ai/docs/integrations/cloudflare

Run the site on your own domain, with the DNS, the certificates and the edge rules staying in the account your team already administers.

Point your own domain at the Commerce site through Cloudflare DNS and keep your own edge in front of it.

|  |  |
| --- | --- |
| Status | **Template**: A prepared recipe on a generic path, which you finish. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | Out: nothing. In: nothing. This is DNS and edge configuration, not a data connection. Kabaido never signs in to your Cloudflare account. |
| What you hand over | The right to create DNS records on your own domain. Kabaido holds no Cloudflare credential. |

### What you get

Run the site on your own domain, with the DNS, the certificates and the edge rules staying in the account your team already administers.

### Connect it

In [Settings then Integrations](/docs/areas/settings#integrations), open the entry and follow its steps:

1. Add your domain here and copy the records Kabaido gives you.
2. Create those records in Cloudflare and set the proxy mode you want.
3. Wait for the certificate to issue, then load the site on your domain.
4. Keep any page rules and firewall rules in Cloudflare where your team can see them.

### More

- On the website: [Cloudflare](/integrations/cloudflare).

## Google Merchant Center

URL: https://kabaido.ai/docs/integrations/google-merchant-center

It would publish the catalogue records you choose as a product feed, so your products appeared in Google's shopping surfaces without a second feed tool.

Not built yet. A Google Merchant Center feed is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Your catalogue exports as CSV today, which Merchant Center takes as a scheduled feed. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Merchant Center account. |

### What you get

It would publish the catalogue records you choose as a product feed, so your products appeared in Google's shopping surfaces without a second feed tool.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Merchant Center](/integrations/google-merchant-center).

## Amazon Business

URL: https://kabaido.ai/docs/integrations/amazon-business

It would publish the catalogue records you choose and bring the orders back as ordinary Kabaido orders under your own numbering.

Not built yet. Selling through Amazon Business is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. Your catalogue exports as CSV today, and an inbound endpoint takes orders from any system that can post them. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Amazon Business seller account. |

### What you get

It would publish the catalogue records you choose and bring the orders back as ordinary Kabaido orders under your own numbering.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Amazon Business](/integrations/amazon-business).

## Trustpilot

URL: https://kabaido.ai/docs/integrations/trustpilot

It would invite a review when an order is delivered and show the score on the site, without anyone exporting a list of customers.

Not built yet. A Trustpilot connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. An outbound endpoint can carry a delivered order into the automation tool you already run, which has a Trustpilot action. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Trustpilot account. |

### What you get

It would invite a review when an order is delivered and show the score on the site, without anyone exporting a list of customers.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Trustpilot](/integrations/trustpilot).

## Google Business Profile

URL: https://kabaido.ai/docs/integrations/google-business-profile

It would keep your opening hours, your locations and your posts in step between the profile and the site, rather than in two places.

Not built yet. A Google Business Profile connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Websites and commerce |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. The Commerce site publishes your own organisation details and structured data today. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Google account. |

### What you get

It would keep your opening hours, your locations and your posts in step between the profile and the site, rather than in two places.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Business Profile](/integrations/google-business-profile).

## Google Analytics 4

URL: https://kabaido.ai/docs/integrations/ga4

It would put your own Google Analytics 4 on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Google Analytics 4 on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) and [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Google Analytics 4 account. |

### What you get

It would put your own Google Analytics 4 on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Analytics 4](/integrations/ga4).

## Google Tag Manager

URL: https://kabaido.ai/docs/integrations/gtm

It would put your own Google Tag Manager on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Google Tag Manager on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Google Tag Manager account. |

### What you get

It would put your own Google Tag Manager on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Tag Manager](/integrations/gtm).

## Microsoft Clarity

URL: https://kabaido.ai/docs/integrations/microsoft-clarity

It would put your own Microsoft Clarity on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Microsoft Clarity on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Microsoft Clarity account. |

### What you get

It would put your own Microsoft Clarity on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Microsoft Clarity](/integrations/microsoft-clarity).

## Plausible

URL: https://kabaido.ai/docs/integrations/plausible

It would put your own Plausible on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Plausible on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Plausible account. |

### What you get

It would put your own Plausible on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Plausible](/integrations/plausible).

## Fathom

URL: https://kabaido.ai/docs/integrations/fathom

It would put your own Fathom on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Fathom on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Fathom account. |

### What you get

It would put your own Fathom on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Fathom](/integrations/fathom).

## Hotjar

URL: https://kabaido.ai/docs/integrations/hotjar

It would put your own Hotjar on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Hotjar on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Hotjar account. |

### What you get

It would put your own Hotjar on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Hotjar](/integrations/hotjar).

## Cookiebot

URL: https://kabaido.ai/docs/integrations/cookiebot

It would put your own Cookiebot on the pages the Wizard embed and your Commerce site serve.

Not built yet. Your own Cookiebot on the Wizard embed and your Commerce pages is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Wizard](/docs/wizard) and [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. The Wizard embed is a Kabaido page in a frame and carries no tag of yours. |
| What you hand over | Nothing to hand over yet. A connection would take an id from your own Cookiebot account. |

### What you get

It would put your own Cookiebot on the pages the Wizard embed and your Commerce site serve.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Cookiebot](/integrations/cookiebot).

## Google Search Console

URL: https://kabaido.ai/docs/integrations/google-search-console

It would let you verify the site and submit its sitemap in your own Google Search Console account.

Not built yet. Verifying your Commerce site in your own Google Search Console is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. |
| What you hand over | Nothing to hand over yet. A connection would take a verification record on your own domain. |

### What you get

It would let you verify the site and submit its sitemap in your own Google Search Console account.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Search Console](/integrations/google-search-console).

## Bing Webmaster Tools

URL: https://kabaido.ai/docs/integrations/bing-webmaster

It would let you verify the site and submit its sitemap in your own Bing Webmaster Tools account.

Not built yet. Verifying your Commerce site in your own Bing Webmaster Tools is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. |
| What you hand over | Nothing to hand over yet. A connection would take a verification record on your own domain. |

### What you get

It would let you verify the site and submit its sitemap in your own Bing Webmaster Tools account.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Bing Webmaster Tools](/integrations/bing-webmaster).

## Schema.org structured data

URL: https://kabaido.ai/docs/integrations/schema-org

It would describe your products and your organisation to search engines from the catalogue records themselves.

Not built yet. Structured data generated from your catalogue records for a Commerce site is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would describe your products and your organisation to search engines from the catalogue records themselves.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Schema.org structured data](/integrations/schema-org).

## llms.txt

URL: https://kabaido.ai/docs/integrations/llms-txt

It would give an assistant reading your site the plain text rather than the page furniture.

Not built yet. An llms.txt generated for your Commerce site is on the roadmap.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Analytics and tags |
| For | [Commerce](/docs/commerce) |
| What moves | Nothing moves yet. |
| What you hand over | Nothing to hand over yet. |

### What you get

It would give an assistant reading your site the plain text rather than the page furniture.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [llms.txt](/integrations/llms-txt).

## SharePoint and OneDrive

URL: https://kabaido.ai/docs/integrations/sharepoint

It would let a drawing, a certificate or a specification live in your own document library and still be the file attached to the quote, the order or the service job.

Not built yet. A SharePoint and OneDrive connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Files and documents |
| For | Every workspace |
| What moves | Nothing moves yet. Attachments upload to Kabaido's own storage today, and the email agent stores what arrives on a message. |
| What you hand over | Nothing to hand over yet. A connection would be a Microsoft sign in scoped to the libraries you choose. |

### What you get

It would let a drawing, a certificate or a specification live in your own document library and still be the file attached to the quote, the order or the service job.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [SharePoint and OneDrive](/integrations/sharepoint).

## Google Drive

URL: https://kabaido.ai/docs/integrations/google-drive

It would let a drawing, a certificate or a specification live in your own Drive and still be the file attached to the quote, the order or the service job.

Not built yet. A Google Drive connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Files and documents |
| For | Every workspace |
| What moves | Nothing moves yet. Attachments upload to Kabaido's own storage today, and the email agent stores what arrives on a message. |
| What you hand over | Nothing to hand over yet. A connection would be a Google sign in scoped to the folders you choose. |

### What you get

It would let a drawing, a certificate or a specification live in your own Drive and still be the file attached to the quote, the order or the service job.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Google Drive](/integrations/google-drive).

## DocuSign

URL: https://kabaido.ai/docs/integrations/docusign

It would send a quote or an agreement for signature and bring the signed document and its audit trail back onto the record.

Not built yet. A DocuSign connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Files and documents |
| For | [Sales Engineer](/docs/sales-engineer) |
| What moves | Nothing moves yet. A quote is accepted on its own tokenised link today, and a project document is signed on a tokenised document link, both of which record who acted and when. |
| What you hand over | Nothing to hand over yet. A connection would run on your own DocuSign account. |

### What you get

It would send a quote or an agreement for signature and bring the signed document and its audit trail back onto the record.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [DocuSign](/integrations/docusign).

## Adobe Acrobat Sign

URL: https://kabaido.ai/docs/integrations/adobe-acrobat-sign

It would send a quote or an agreement for signature and bring the signed document and its audit trail back onto the record.

Not built yet. An Adobe Acrobat Sign connection is on the roadmap with no date.

|  |  |
| --- | --- |
| Status | **Roadmap**: Not built yet. Tell us what you need and we will talk it through. |
| Kind | Files and documents |
| For | [Sales Engineer](/docs/sales-engineer) |
| What moves | Nothing moves yet. A quote is accepted on its own tokenised link today, and a project document is signed on a tokenised document link, both of which record who acted and when. |
| What you hand over | Nothing to hand over yet. A connection would run on your own Adobe account. |

### What you get

It would send a quote or an agreement for signature and bring the signed document and its audit trail back onto the record.

### Asking for it

This connection is not built yet. [Tell us](/contact) what you need it to do; until then the [universal paths](/docs/integrations/connecting-other-systems) reach any system with an API.

### More

- On the website: [Adobe Acrobat Sign](/integrations/adobe-acrobat-sign).

# Docs: API and webhooks

## API keys and scopes

URL: https://kabaido.ai/docs/api/api-keys-and-scopes

Create a key that can do exactly what one integration needs, and retire it safely.

Why: Every call to the API or the MCP server has to prove which workspace it belongs to and what it may touch.
What: An API key begins `kbd_`, belongs to one organisation and carries a set of scopes.
How: Create it on the **Kabaido API** entry in Settings and send it as a Bearer token.

### Create a key

1. Open `/app/settings/integrations` and open **Kabaido API**. Keys need the admin role or above; every plan has them.
2. Choose **New key**, name it after the integration that will use it and tick its **Scopes**.
3. Choose **Create key** and copy it. This is the only time the full key is shown.

### Send it

```bash
curl "https://kabaido.ai/api/v1/products?search=blade&limit=50" \
  -H "Authorization: Bearer kbd_your_key_here"
```

A missing, unknown or revoked key gets 401. A key without the scope a route needs gets 403.

### Scopes

| Scope | Allows | Also needs |
| --- | --- | --- |
| `products:read` | List and search products |  |
| `products:write` | Bulk upsert products by SKU |  |
| `quotes:read` | List quotes and read one with its lines |  |
| `quotes:write` | Reserved: no route or tool uses it yet |  |
| `orders:read` | List orders and read one with its lines |  |
| `customers:read` | List customers and read one with its contacts |  |
| `customers:write` | Upsert customers |  |
| `requests:read` | List requests and read one with its messages |  |
| `requests:write` | Open a request from enquiry text |  |
| `stock:read` | Read stock lines, locations and the movement ledger | [Stock](/docs/stock) |
| `stock:write` | Record a stock movement through the ledger | [Stock](/docs/stock) |
| `deliveries:read` | Read deliveries with their lines and packages | [Route](/docs/route) |
| `suppliers:read` | Read suppliers and their contacts | [Source](/docs/source) |
| `purchase_orders:read` | Read purchase orders with their lines and receipts | [Source](/docs/source) |

### Keeping keys safe

- Kabaido stores only a hash of each key, so a lost key cannot be recovered: create a new one.
- The list shows each key's first characters and when it was last used. Revoking takes effect at once.
- Make one key per integration, scoped to what it does: a nightly catalogue push needs `products:write` and nothing else.

### Rotating a key

There is no rotate button. Create the new key, deploy it, watch **last used** move to it, then revoke the old one.

## The REST API

URL: https://kabaido.ai/docs/api/the-rest-api

Call every v1 resource with the right scope, page through lists and handle every error it returns.

Why: Your own systems should read what your team works on and write what they are allowed to, without anyone copying data.
What: REST over HTTPS at `https://kabaido.ai/api/v1`, scoped to your organisation by the key, with money in integer minor units.
How: Create a scoped key, then call the routes below with an `Authorization: Bearer` header.

The machine readable description is the OpenAPI document at `https://kabaido.ai/api/v1/openapi.json` (version 1.0.0).

### Resources

| Method | Path | Scope | What it does |
| --- | --- | --- | --- |
| GET | `/api/v1/products` | `products:read` | List products |
| POST | `/api/v1/products/bulk` | `products:write` | Bulk upsert products |
| GET | `/api/v1/quotes` | `quotes:read` | List quotes |
| GET | `/api/v1/quotes/{id}` | `quotes:read` | Get a quote with lines |
| GET | `/api/v1/orders` | `orders:read` | List orders |
| GET | `/api/v1/orders/{id}` | `orders:read` | Get an order with lines |
| GET | `/api/v1/stock/lines` | `stock:read` | List stock lines |
| GET | `/api/v1/stock/lines/{id}` | `stock:read` | Get a stock line with its movements |
| GET | `/api/v1/stock/locations` | `stock:read` | List stock locations |
| GET | `/api/v1/stock/movements` | `stock:read` | List stock movements |
| POST | `/api/v1/stock/movements` | `stock:write` | Record a stock movement |
| GET | `/api/v1/deliveries` | `deliveries:read` | List deliveries |
| GET | `/api/v1/deliveries/{id}` | `deliveries:read` | Get a delivery with its lines and packages |
| GET | `/api/v1/suppliers` | `suppliers:read` | List suppliers |
| GET | `/api/v1/suppliers/{id}` | `suppliers:read` | Get a supplier with contacts |
| GET | `/api/v1/purchase-orders` | `purchase_orders:read` | List purchase orders |
| GET | `/api/v1/purchase-orders/{id}` | `purchase_orders:read` | Get a purchase order with lines and receipts |
| GET | `/api/v1/customers` | `customers:read` | List customers |
| POST | `/api/v1/customers` | `customers:write` | Upsert customers |
| GET | `/api/v1/customers/{id}` | `customers:read` | Get a customer with contacts |
| GET | `/api/v1/requests` | `requests:read` | List requests |
| POST | `/api/v1/requests` | `requests:write` | Create a request |
| GET | `/api/v1/requests/{id}` | `requests:read` | Get a request with messages |

The stock routes also need [Stock](/docs/stock), the deliveries routes [Route](/docs/route) and the suppliers and purchase orders routes [Source](/docs/source). Without the product a route answers 404. Reads keep working after a product is switched off while it still holds rows; a stock movement needs Stock on.

### Pages

A list returns its rows and `next_cursor`. Pass that back as `cursor` for the next page; null means you have everything. Products are ordered by SKU, stock locations come back whole with the default first, and every other list is newest first. `limit` sets the page size, up to the caps on [rate limits](/docs/api/rate-limits).

### Examples

Read a quote:
```bash
curl https://kabaido.ai/api/v1/quotes/7f0c0000-0000-0000-0000-000000000000 \
  -H "Authorization: Bearer kbd_your_key_here"
```
The quote comes with its `lines` in position order. Each line carries `amount_minor`, its net value: use it rather than recomputing from `qty` and `unit_price_minor`, because a seller can pin a line total (`amount_override_minor`).
Open a request:
```bash
curl -X POST https://kabaido.ai/api/v1/requests \
  -H "Authorization: Bearer kbd_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "text": "Please quote 20 off 250 mm saw blades, 60 teeth" }'
```
Returns 201 with the request's `id`, `title` and `url`. The text may run to 100,000 characters. The request is attributed to the organisation's owner and opens at that `url` in the [AI area](/docs/areas/ai). Opening it through a key draws no usage.
Record stock:
```bash
curl -X POST https://kabaido.ai/api/v1/stock/movements \
  -H "Authorization: Bearer kbd_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "receipt", "product_id": "<product id>", "qty": 20, "unit_cost_minor": 1250, "idempotency_key": "grn-4411-1" }'
```
A key may write the kinds a person writes by hand: `adjustment`, `transfer`, `scrap`, `return` and `receipt`. Name the `line_id`, or the `product_id` with a `location_id` when it is not the default location; a transfer also names `to_location_id`. A repeated `idempotency_key` is not written twice. See [the ledger](/docs/stock/movements-and-the-ledger).

### Writes

`POST /api/v1/products/bulk` upserts up to 10,000 products by SKU. `POST /api/v1/customers` upserts up to 500 customers, matched by external id then email domain. A retry after a timeout updates rather than duplicates, except for a customer sent with neither an `external_id` nor an email: that one is created again.

### Errors

An error is JSON with one `error` message.

| Status | Means |
| --- | --- |
| 400 | The query, the body or the cursor is not valid |
| 401 | The key is missing, unknown or revoked |
| 402 | Your existing products plus the bulk batch would pass your plan's product cap |
| 403 | The key lacks the scope |
| 404 | Not in your organisation, or the product the route needs is off |
| 409 | A stock movement would take a balance below zero |
| 413 | Too many products in one bulk call |
| 422 | A request cannot be attributed: the organisation has no owner |
| 429 | The key's rate limit; wait and retry |
| 500 | A fault on our side; retry with a backoff |

> Every money field is an integer in minor units beside a `currency`: `total_minor` 58200 with `currency` GBP is 582.00 pounds. Divide at display, not before.

## Webhooks

URL: https://kabaido.ai/docs/api/webhooks

Receive signed events at your own URL and prove each one came from Kabaido.

Why: Your own system should hear about a quote or an order the moment it happens, not when somebody polls.
What: Kabaido posts a signed JSON event to each endpoint that subscribes to it.
How: Add an endpoint on **Custom outbound webhook**, choose its events and verify the signature on your side.

### Add an endpoint

1. In `/app/settings/integrations`, open **Custom outbound webhook** (or Slack, Microsoft Teams, Zapier, Make or n8n) and choose **Add endpoint**. It needs the admin role.
2. Enter the **Endpoint URL**, pick the **Events** (none picked means all events) and the **Body format**.
3. Copy the signing secret. It is shown once.

### Events

Event names are never renamed; new ones are only added.

| Event | Fires when |
| --- | --- |
| `quote.created` | A quote is created |
| `quote.sent` | A quote is sent to the customer |
| `quote.accepted` | A quote is accepted |
| `quote.declined` | A quote is declined |
| `order.created` | An order is created |
| `order.updated` | An order changes status (other than to cancelled), is edited or is emailed |
| `order.cancelled` | An order is cancelled |
| `service_item.updated` | A service item changes |
| `design.saved` | A design is saved |
| `design.exported` | A design is exported |
| `quote.superseded` | A quote is replaced by a new version |
| `quote.expired` | A quote passes its valid until date |
| `quote.viewed` | The customer opens the quote |
| `order.invoiceable` | An order is fulfilled, so an invoice can be raised |
| `purchase_order.sent` | A purchase order is sent to the supplier |
| `purchase_order.received` | Goods are received against a purchase order |
| `order.dispatched` | An order's goods leave |
| `order.delivered` | An order is delivered |
| `delivery.dispatched` | A consignment is dispatched |
| `delivery.completed` | A consignment is delivered |
| `delivery.failed` | A delivery attempt fails |
| `monitor.fired` | A monitor's condition is met |

### Payload and headers

```json
{
  "event": "quote.accepted",
  "data": {
    "quote_id": "7f0c0000-0000-0000-0000-000000000000",
    "number": "Q-1042",
    "customer_id": "3a1e0000-0000-0000-0000-000000000000",
    "total_minor": 58200,
    "currency": "GBP"
  },
  "org_id": "00000000-0000-0000-0000-000000000000"
}
```

What `data` holds depends on the event and on where it happened: read the fields you need and ignore the rest.

`X-Kabaido-Event` carries the event name. `X-Kabaido-Signature` is `t=<unix seconds>,v1=<hex>`, where the hex is an HMAC SHA-256 of the timestamp, a full stop and the raw body, keyed by the signing secret.

### Verify the signature

TypeScript:
```typescript
import { createHmac, timingSafeEqual } from "node:crypto";

// header: the X-Kabaido-Signature value, "t=<unix seconds>,v1=<hex>"
// rawBody: the request body exactly as received, before any JSON parsing
export function verify(secret: string, header: string, rawBody: string): boolean {
  const match = /^t=(\d+),v1=([0-9a-f]+)$/.exec(header.trim());
  if (!match) return false;
  const [, t, v1] = match;
  if (Math.abs(Date.now() / 1000 - Number(t)) > 300) return false; // five minutes
  const expected = createHmac("sha256", secret).update(`${t}.${rawBody}`).digest();
  const received = Buffer.from(v1, "hex");
  return received.length === expected.length && timingSafeEqual(received, expected);
}
```
Python:
```python
import hashlib, hmac, re, time

# header: the X-Kabaido-Signature value; raw_body: the body bytes as received
def verify(secret: str, header: str, raw_body: bytes) -> bool:
    match = re.fullmatch(r"t=(\d+),v1=([0-9a-f]+)", header.strip())
    if not match:
        return False
    t, v1 = match.groups()
    if abs(time.time() - int(t)) > 300: # five minutes
        return False
    expected = hmac.new(secret.encode(), t.encode() + b"." + raw_body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(v1, expected)
```

> Sign over the raw body bytes, before any JSON parsing: a reserialised body will not match.

### Delivery and retries

A delivery succeeds on any 2xx answer within 10 seconds. A failed one is tried again by the platform's nightly run, up to five attempts in all. **Recent deliveries** on the endpoint shows each status, with **Retry** to send one now. Answer fast and do the work after.

### Body formats

The signed JSON envelope is the default. **Slack message (incoming webhook)** and **Microsoft Teams card (Workflows)** post readable messages instead; those services ignore the signature, so the URL itself is the secret.

## Inbound endpoints

URL: https://kabaido.ai/docs/api/inbound-endpoints

Give any system a URL it can post JSON to, and choose what each post does.

Why: Plenty of systems can send an HTTP post but cannot hold a key or read an API.
What: A tokenised URL under `/api/in/` that accepts JSON and does one action.
How: Create it on **Custom inbound endpoint**, pick the action and point your sender at the URL.

### Create one

1. In `/app/settings/integrations`, open **Custom inbound endpoint** and choose **New endpoint**. It needs the admin role.
2. Name it, choose the **Action** and, if the sender can set a header, tick **Require a signature**.
3. Choose **Create endpoint**, then copy the **URL** and the **Secret**. The secret is shown once.

### Actions

| Action | Body | What happens |
| --- | --- | --- |
| Create request | `{ text, title?, customer?: { company?, email? }, external_ref? }` | Each post opens a request in the AI area, ready to answer. |
| Upsert customers | `{ customers: [{ company, email?, phone?, external_id? }] }`, up to 500 | Create or update customers matched by external id or email domain. |
| Upsert products | `{ products: [...], schema_id? }`, up to 1,000 | Create or update catalogue products by SKU, with the same validation as the import wizard. |
| ERP order status | `{ quote_ref?, order_ref?, status, tracking_url? }` | An ERP such as EFACS posts an order status update; the matched order moves with it. |
| Order invoice | `{ order_ref?, quote_ref?, invoice_ref, invoice_status?, amount_minor?, currency? }` | Your accounting system posts the invoice it raised. Wire it from Xero, QuickBooks or Sage through the automation you already run; Kabaido records the reference, it never issues an invoice. |
| Purchase order acknowledgement | `{ po_number, supplier_ref?, lines?: [{ position?, expected_date }] }` | A supplier or a broker posts our purchase order number, their reference and confirmed dates; the order moves to acknowledged. |
| Supplier invoice | `{ po_number, invoice_ref, amount_minor?, currency?, invoiced_qty? }` | Your accounting system posts the supplier's invoice against our purchase order number; the three way match runs and a variance is raised where it does not agree. |
| Delivery status | `{ delivery_ref?, consignment_ref?, order_ref?, status, tracking_url? }` | A carrier account, an aggregator or an ERP posts what happened to a consignment, matched by the delivery number, the consignment reference or the order. The delivery moves, the tracking address is stored on it and the order follows. |

### Example

```bash
curl -X POST https://kabaido.ai/api/in/whin_your_token \
  -H "Content-Type: application/json" \
  -d '{ "text": "RFQ: 25 off 12 mm carbide end mills, 4 flute", "external_ref": "WEB-2291" }'
```

### Signatures

With **Require a signature** on, send `X-Kabaido-Signature` built exactly as [webhook signatures](/docs/api/webhooks) are, with the endpoint's secret and a timestamp within five minutes. Without it, the token in the URL is the only credential: treat the URL like a password.

### Responses

| Status | Means |
| --- | --- |
| 200 | Done; the body summarises what changed |
| 202 | Accepted: a request was opened, or nothing matched yet |
| 400 | The body is not valid JSON or not the action's shape |
| 401 | A signature is required and is missing or wrong |
| 404 | No endpoint has that token |
| 402 | An upsert of products would pass your plan's product cap |
| 409 | The endpoint is paused, or the record cannot move that way |
| 413 | The body is over 1MB |
| 422 | Understood but not applicable: an unknown status, an invoice that does not fit, or no owner to attribute a request to |
| 429 | Too many posts at once; see [rate limits](/docs/api/rate-limits) |
| 500 | A fault on our side; retry later |

Every post that reaches the action, accepted or rejected, appears under **Recent receipts** on the endpoint, so a sender posting the wrong shape shows up in Settings. Untick **Active** to pause a sender that has gone wrong; deleting the endpoint destroys the token for good.

## The MCP server

URL: https://kabaido.ai/docs/api/mcp

Connect Claude or any MCP client to your workspace, with the scopes you choose.

Why: Asking which open quotes belong to customers who have not ordered since March is one sentence to an assistant and four screens anywhere else.
What: A Model Context Protocol server at `https://kabaido.ai/api/mcp` over streamable HTTP, with read tools and one tool that opens requests.
How: Add it to Claude as a custom connector, or give any MCP client an API key.

### Connect

Claude (web and desktop):
1. In Claude, open Settings, then Connectors, then Add custom connector.
2. Paste `https://kabaido.ai/api/mcp` and continue.
3. Sign in to Kabaido, pick the organisation and the scopes, then Allow access.
Claude Code:
Create a key on **Kabaido API**, then run:
```bash
claude mcp add --transport http kabaido https://kabaido.ai/api/mcp \
  --header "Authorization: Bearer kbd_your_key_here"
```
Cursor and other clients:
```json
{
  "mcpServers": {
    "kabaido": {
      "url": "https://kabaido.ai/api/mcp",
      "headers": { "Authorization": "Bearer kbd_your_key_here" }
    }
  }
}
```

The Claude connector signs in with OAuth and PKCE, so no key is pasted anywhere. Approved connections are listed under **Active connections** on the **Claude** and **Any MCP client** entries, each of which can be revoked.

### Tools

| Tool | Scope | What it does |
| --- | --- | --- |
| `search_products` | `products:read` | Search the catalogue by text, SKU or category |
| `get_product` | `products:read` | One product with its attributes, by id or SKU |
| `list_quotes` | `quotes:read` | Recent quotes, by status |
| `get_quote` | `quotes:read` | One quote with its lines, by id or number |
| `list_orders` | `orders:read` | Recent orders, by status |
| `get_order` | `orders:read` | One order with its lines, by id or number |
| `search_customers` | `customers:read` | Customers by company or domain |
| `list_requests` | `requests:read` | Recent requests |
| `create_request` | `requests:write` | Open a request from enquiry text |
| `read_stock_balance` | `stock:read` | On hand, reserved, free and on order for one product; needs [Stock](/docs/stock) |
| `read_stock_shortages` | `stock:read` | Lines at or under their reorder point; needs [Stock](/docs/stock) |
| `list_deliveries` | `deliveries:read` | Consignments by order, customer or state; needs [Route](/docs/route) |

### The scope ceiling

A connection can never hold more than the person approving it: the consent screen offers only the scopes their own role allows. An operator's connector reads requests and nothing commercial.

### Usage

Reading costs nothing. `create_request` through an API key is free, as on the REST API. Through an OAuth connector it draws on [your usage](/docs/billing/how-usage-works) at twice the standard weight. With too little usage left, the tool says so rather than failing silently.

> Treat a connection like a key. Grant read scopes by default and add `requests:write` only where an assistant should raise requests.

## Rate limits

URL: https://kabaido.ai/docs/api/rate-limits

Know every limit the API, the inbound endpoints and the webhooks apply, and what happens at each.

Why: A limit you know about is a retry you can plan; one you discover is an outage.
What: Token bucket limits per key and per endpoint, plus caps on page sizes and batch sizes.
How: Read the tables, back off on 429 and page with `cursor` rather than asking for everything at once.

### Request rates

| Surface | Limit | Over it |
| --- | --- | --- |
| REST API, `/api/v1` | 600 requests a minute per key. The whole minute's allowance may arrive as one burst; it refills evenly. | 429 `Rate limited` |
| Inbound endpoint, `/api/in/` | Bursts of up to 120 posts per endpoint, refilling at two a second | 429 `Rate limited` |

The REST limit is counted per key, so two integrations on two keys never slow each other. Every call counts, whichever route it hits.

### Page sizes

| List | Default | Most per page |
| --- | --- | --- |
| `/api/v1/products` | 100 | 500 |
| `/api/v1/quotes` | 50 | 200 |
| `/api/v1/orders` | 50 | 200 |
| `/api/v1/stock/lines` | 50 | 200 |
| `/api/v1/stock/movements` | 50 | 200 |
| `/api/v1/deliveries` | 50 | 200 |
| `/api/v1/suppliers` | 50 | 200 |
| `/api/v1/purchase-orders` | 50 | 200 |
| `/api/v1/customers` | 100 | 500 |
| `/api/v1/requests` | 50 | 200 |

### Batch and body sizes

| Call | Most |
| --- | --- |
| `POST /api/v1/products/bulk` | 10,000 products (413 above it) |
| `POST /api/v1/customers` | 500 customers |
| `POST /api/v1/requests` | 100,000 characters of text |
| Inbound endpoint | A 1MB body (413 above it); 500 customers or 1,000 products per post |

### Outbound webhooks

Each delivery waits 10 seconds for your answer. A failed delivery is tried again in the nightly run, up to five attempts in all.

### Retrying well

- On 429 or 5xx, wait and retry with a growing pause.
- Never retry a 4xx unchanged: it fails the same way.
- Products upsert by SKU and customers by external id or email domain, so a retried batch updates rather than duplicates. Give every customer an `external_id` to be sure.

## API changelog

URL: https://kabaido.ai/docs/api/api-changelog

See what the API, the webhooks and the MCP server offer today and when each part arrived.

Why: An integration you build today should keep working, and you should know what is new.
What: The API's own history: every change so far has been an addition, and nothing shipped has been renamed or removed.
How: Read the entries since you last built against the API; the paths stay under `/api/v1`.

### Where it stands

The REST API is v1 and its OpenAPI document is version 1.0.0: 23 operations and 14 scopes, with 22 webhook events and 8 inbound actions. Scope, event and action names only ever grow.

### History

| Date | What arrived |
| --- | --- |
| 2026-06-10 | API keys with scopes. `POST /api/v1/products/bulk` and `GET /api/v1/products`. Signed outbound webhooks for quotes, orders and service items. |
| 2026-06-12 | Quotes, orders, customers and requests on v1, with their scopes and the OpenAPI document. Inbound endpoints: create request, upsert customers and upsert products. The MCP server at `/api/mcp`. The Slack and Teams body formats. |
| 2026-06-13 | The `quote.declined` and `order.updated` events. |
| 2026-06-23 | The ERP order status inbound action. |
| 2026-08-27 | The `design.saved`, `design.exported`, `quote.superseded`, `quote.expired`, `quote.viewed` and `order.invoiceable` events. The order invoice inbound action. |
| 2026-09-20 | Stock: `stock:read`, `stock:write`, the stock lines, locations and movements routes and two MCP tools. Source: `suppliers:read`, `purchase_orders:read`, their routes, the two `purchase_order` events and two inbound actions. Route: `deliveries:read`, the deliveries routes, five delivery events, the delivery status action and `list_deliveries`. Monitoring: `monitor.fired`. |

Each date is the day the change reached the codebase, from its history.

# Docs: Billing and usage

## Plans and usage

URL: https://kabaido.ai/docs/billing/plans-and-usage

Pick the plan that fits: every plan carries every product, and plans differ only in usage and scale.

Why: A plan should buy capacity, not permission, so nobody pays to unlock a product they need.
What: Five plans: Free, Pro (£189 a month), Ultra (£549), Max (£1,299) and Enterprise by agreement.
How: Every product is on every plan and switched on by need; the plan sets the month's usage and the scale caps.

### The ladder

| Plan | A month | Usage |
| --- | --- | --- |
| Free | £0 | A small allowance for the life of the account |
| Pro | £189 | A month of usage for a desk that quotes through the day |
| Ultra | £549 | three and a half times the usage of Pro |
| Max | £1,299 | eight and a half times the usage of Pro |
| Enterprise | By agreement | An agreed usage budget |

No VAT is charged: Kabaido Ltd is not VAT registered yet. Annual billing takes 5 per cent off: Pro is £2,154.60 a year, a saving of £113.40.

### What scales

|  | Free | Pro | Ultra | Max |
| --- | --- | --- | --- | --- |
| Users | 2 | Unlimited | Unlimited | Unlimited |
| Catalogue products | 100 | 10,000 | 100,000 | 1,000,000 |
| Services | 2 | 25 | Unlimited | Unlimited |
| Design modules | 2 | Unlimited | Unlimited | Unlimited |
| Saved designs | 5 | 250 | 2,500 | 25,000 |
| Design exports a month | 10 | 250 | 1,000 | Fair use |
| Wizard runs a month | 10 | Unlimited | Unlimited | Unlimited |
| Stations | 1 | 2 | 5 | 15 |
| Storage | 250 MB | 10 GB | 50 GB | 250 GB |
| Inspect profiles | Preview | On the same usage | On the same usage | On the same usage |
| Your customers on your own address | Path form only | Included | Included | Included |
| Documents | Kabaido footer | Your branding alone | Your branding alone | Your branding alone |
| Implementation sessions | 0 | 0 | 1 | 2 |
| Support | Docs | Email | Priority email | Priority, named contact |

> A plan gates usage and scale, never a product. The API, webhooks, the MCP connector, CSV import and export and the quote portal are on every plan, free included.

The live figures for your own workspace are on `/app/settings/billing`, and the public comparison is on [the pricing page](/pricing).

## How usage works

URL: https://kabaido.ai/docs/billing/how-usage-works

Know what draws on the month's usage, what never does and what happens when it is spent.

Why: One pool is simpler to plan for than a price list of actions.
What: A month of usage covering the AI and the platform together, shown as a share of the month and never as a count.
How: Each plan's pool is sized from a modelled budget for the AI provider's cost, and platform activity draws a small share from the same pool.

Screenshot of /app/settings/billing: Settings then Billing: the current plan, the usage bar for the month and the daily budget.

### What draws on it

| Draws | Examples |
| --- | --- |
| Most | AI work: reading a request, matching its lines, drafting a quote or a reply. A scanned drawing draws more than a pasted email, and an answer that needs the larger model draws more than one that does not. |
| About one AI answer | Opening an Inspect company profile. An Inspect export draws more. |
| A touch | A record created or changed, a wizard run, an import, a design export, a monitor that sends an email. |
| Nothing | Browsing, searching, filtering, reading, opening a station screen, scanning a code, rendering a document and your customers reading their own records. |

[The customer AI](/docs/commerce/the-customer-ai) on the Commerce surface draws on the same pool, and the usage card shows it as its own line, **Your customers**.

### Where you see it

- The usage bar at the top right of the AI input on `/app`. Hover, focus or click it for the card: this month's share, today's budget when one is set, **What has used it** and the reset date.
- `/app/settings/billing`, under **Usage**, measured over the billing period rather than the calendar month.
- The Inspect header, with the same bar.

Interactive example: Three worked example months, one per firm, each drawing on its own pool and shown as shares.

### When it is spent

There is no overage on any plan. AI answers pause until the reset, and quoting, the catalogue and everything you do by hand carry on. An upgrade refreshes usage straight away.

> Usage resets on your billing date and does not roll over. The free plan's allowance is for the life of the account and does not refresh.

## Daily budgets

URL: https://kabaido.ai/docs/billing/daily-budgets

Cap what the AI may use in a day so one busy day cannot spend the month.

Why: A batch of large drawings or a loop in an integration can draw on a month's usage in an afternoon.
What: An optional cap on the AI's use per day, set as a share of the month's allowance.
How: The owner picks a preset on the Billing page; the AI checks the day's budget before the month's balance.

### Set a budget

1. Open `/app/settings/billing` as the organisation owner and find **Daily budget**.
2. Under **Budget**, choose **Off**, **A fifth of the month**, **A tenth of the month**, **A thirtieth of the month** or **Custom**.
3. For **Custom**, move the slider: from half a thirtieth to the whole month.
4. Choose **Save budget**.

### What happens on the day

- The usage card shows how much of today's budget is used, as a share.
- When it is spent, AI answers pause with "Today's budget for AI is used up" and resume after midnight.
- Everything done by hand carries on. A budget never stops quoting, a station or a delivery.
- The day starts at midnight in the organisation's timezone, shown under the budget. It is Europe/London by default.

> Only the owner sets a budget; an admin can read it. The free plan has no billing period, so it has no daily budget.

## Changing plans

URL: https://kabaido.ai/docs/billing/changing-plans

Upgrade, downgrade, switch to annual or cancel, knowing what changes at once and that nothing is deleted.

Why: A workspace grows and shrinks, and the plan should follow without losing any work.
What: Every change of plan takes effect at once, and no record is ever deleted to fit a smaller plan.
How: The owner changes plan from **Plans** on `/app/settings/billing`; payment methods, invoices and cancelling live in the Stripe portal.

### Change plan

1. Open `/app/settings/billing` as the owner and scroll to **Plans**.
2. Pick **Monthly** or **Annual** under **Billing period**.
3. Choose **Upgrade** or **Switch** on the plan you want. A first paid plan opens a secure Stripe checkout instead.

### What changes when

| Change | Charge | Usage | Scale caps |
| --- | --- | --- | --- |
| Upgrade | Prorated: the difference for the rest of the period | Raised to the new plan's month straight away | The larger caps apply at once |
| Downgrade | No mid period charge and no refund for time already paid | Kept until the next period starts at the smaller allowance | The smaller caps apply at once |

The period you pick travels with the plan you choose. The card of your current plan reads **Current plan** and cannot be chosen again.

Because a downgrade applies at once, the best time to move down is close to your renewal date.

### Over a cap after a downgrade

Nothing is deleted. If the catalogue holds more products than the new cap, it turns read only above the cap and a banner says so; editing returns when you remove products or move back up.

### Cancelling

Choose **Manage payment and invoices** to open the Stripe portal, where you cancel, update the card and download invoices. When the subscription ends the workspace returns to the free plan with its data intact. Deleting the organisation is separate: see [Data export and deletion](/docs/security/data-export-and-deletion).

> Only the owner changes the plan. A failed payment gives seven days to update the card before AI answers pause; the rest of the platform stays available.

## The free plan caps explained

URL: https://kabaido.ai/docs/billing/the-free-plan-caps-explained

Know what the free plan holds, why its AI allowance is small and what stops when it is spent.

Why: The free plan exists so you can see the platform work on your own enquiry before you pay.
What: Every product, a small AI allowance for the life of the account and tight scale caps. No card needed.
How: Two guards bound the AI, a usage allowance and a cap on provider cost, and it stops at whichever comes first.

### The scale caps

| Cap | Free |
| --- | --- |
| Users | 2 |
| Catalogue products | 100 |
| Services and design modules | 2 and 2 |
| Saved designs | 5 |
| Design exports and wizard runs a month | 10 and 10 |
| Stations | 1 |
| Storage | 250 MB |
| Inspect | Preview: the map and the lists, no company profile opened |
| Your customers | The path form of the customer surface only |

### The AI allowance

- Enough for a few real enquiries. It does not refresh: the free plan is a look, not a rolling trial.
- Each free request is bounded: a shorter document, fewer knowledge packs and no step up to the larger model.
- The guard checks before a request starts and again during it, so one large document cannot run past it.

### When it is spent

AI answers pause and say why. Everything else carries on: the catalogue, quoting by hand and what was already read. Nothing is deleted at a cap and you are never billed for going over one.

> Upgrading from `/app/settings/billing` lifts the caps to the new plan's and gives a full month of usage the moment the payment lands.

## Enterprise

URL: https://kabaido.ai/docs/billing/enterprise

Know what an Enterprise agreement adds beyond Max and how to start the conversation.

Why: Some workspaces outgrow Max in usage, catalogue size, stations or regions.
What: An agreement on top of Max: an agreed usage budget and scale caps, invoicing on your terms and a named contact.
How: Book a walkthrough from the Enterprise card on the pricing page or the Billing page; the terms are then set on your workspace by Kabaido.

### What it can include

- An agreed monthly usage budget beyond Max.
- Raised scale caps: catalogue products, stations, storage and Inspect regions.
- Invoicing annually or quarterly, on a twelve month minimum.
- A data processing agreement.
- A named contact and an agreed implementation.

### Usage beyond the budget

There is no overage on any published plan. An Enterprise agreement may carry one, and only there: Kabaido sets the `overage_allowed` override on your workspace, and usage past the agreed budget is billed as the agreement says.

### Start the conversation

1. On `/app/settings/billing`, choose **Talk to us about Enterprise**, or **Book a walkthrough** on [the pricing page](/pricing).
2. Pick a time; the meeting runs on Google Meet.

> Enterprise pricing is by agreement and never published. Every product stays on the plan, as on every other plan.

## Work quoted per project

URL: https://kabaido.ai/docs/billing/work-quoted-per-project

Know the one off work that sits beside a subscription and how each piece is priced.

Why: Some work is built once for one business and does not belong in a monthly price.
What: One off work built for your business, each piece quoted per project and always separate from the plan.
How: We scope it with you in a proposal beside the subscription, which stays the same.

| Work | For | Price |
| --- | --- | --- |
| A Commerce build | Your website built on Commerce, billed as two invoices, then run on your plan | £6,500 to £12,500 per project |
| A custom design module | A product you make to order that no preset covers | Quoted per project |
| A custom wizard module | Selection logic your customers need walking through | Quoted per project |
| A custom machine module | A machine on your floor that no preset runs | Quoted per project |
| A custom service model | A service you sell that no preset models | Quoted per project |

Once built, each piece works like any preset and runs on your ordinary plan with no hosting line or extra subscription.

> There is no other recurring line. A station at a machine or a bench is a scale cap on the plan, not a priced extra.

# Docs: Security and data

## Security overview

URL: https://kabaido.ai/docs/security/overview

See in one table how Kabaido isolates, encrypts and protects your commercial data.

Why: A quote shows what a business buys, from whom, at what margin and for which customer.
What: The practices in force today, in enough detail for a security review.
How: Isolation lives in the database, not in application code, so a missed filter cannot leak another organisation's rows.

### The model in one view

| Layer | Practice |
| --- | --- |
| Isolation | Every row is organisation scoped under row level security in Postgres. Storage paths start with the organisation's id. |
| Encryption | TLS in transit, AES-256 at rest, and integration credentials encrypted again by the application. |
| Access | Ranked roles enforced by the database, owner safeguards and an audit log of administrative actions. |
| Your customers | A separate principal that is never a member of your organisation. See [the customer facing trust boundary](/docs/security/the-customer-facing-trust-boundary). |
| AI | Anthropic only, whose commercial terms bar training its models on customer content. Every value is cited or left empty. |
| Hosting | Database and files in the EU (AWS Frankfurt, eu-central-1); the application runs in London. |
| Payments | Stripe holds card details. Kabaido never sees them. |
| Your data | Export at any time; deletion by the owner or on request. |

Every plan runs on the same shared infrastructure with the same isolation. There is no dedicated or customer held key tier today.

> Every provider Kabaido runs on holds SOC 2 Type II, and the database, hosting and AI hold ISO 27001 too. [The security page](/security) links each provider's own page so you can check.

## Tenant isolation and access control

URL: https://kabaido.ai/docs/security/tenant-isolation-and-access-control

See how organisation scoping is enforced at the database and who can do what inside your account.

Why: An application filter is a line somebody can forget to write.
What: Row level security on every table and every storage path, plus ranked roles inside your organisation.
How: Postgres checks your membership and role on every read and write, including ones nobody thought about.

### Rows and files

- Every table that holds organisation data carries an organisation id; a session sees only rows of organisations it belongs to.
- Every stored file path begins with the owning organisation's id, and the storage policies apply the same checks.
- Write policies are ranked: the catalogue needs engineer or above, settings and integrations admin or above, billing the owner.

Interactive example: The table policy, the storage path rule and the role ladder.

### Roles

Roles, lowest to highest: viewer, operator, sales, engineer, admin and owner. An operator works at stations and never sees a price. A role template gives a person their role, areas and stations in one step; see [Users, roles and stations](/docs/getting-started/users-roles-and-permissions).

The last owner cannot be demoted or removed, and only an owner grants ownership. One login can belong to several organisations with a role in each, and a role in one grants nothing in another.

### Elevated access on the server

A few server jobs act outside a user session: payment webhooks, import workers, the AI pipeline, scheduled jobs and the token links such as the quote portal. Each is scoped to one named organisation or one record, and the elevated key never reaches the browser.

### Audit

Administrative actions, bulk catalogue edits included, are logged with the actor and what changed. The log is written by the server, so a user can cause an entry but never author or edit one.

> Isolation protects one organisation from another. Within your own, roles decide what each person can see and export.

## Encryption and credentials

URL: https://kabaido.ai/docs/security/encryption-and-credentials

Know how data, keys and secrets are encrypted, hashed and verified end to end.

Why: Encryption at rest protects the disk but does nothing about a query.
What: TLS in transit, AES-256 at rest and a second layer for anything that works as a credential.
How: Secrets are encrypted or hashed by the application before they are written, with a key held outside the database.

### What protects what

| Item | Protection |
| --- | --- |
| All traffic | TLS, to the app, the API and between providers. |
| Database and files | AES-256 at rest. |
| Integration credentials and connected inbox or calendar tokens | Encrypted again with AES-256-GCM before they are stored. A database read alone cannot recover one. |
| API keys | Shown once, stored only as a hash with a server held secret, scoped, revocable and stamped with their last use. |
| Outbound webhooks | Signed with HMAC SHA-256 over a timestamp and the raw body, with a per endpoint secret shown once. |
| Inbound endpoints | Long random tokens, with optional signature checks. Pausing or deleting revokes the URL at once. |
| Quote portal and document links | An unguessable token scoped to one record, rate limited against scanning. |

Verification examples for webhooks are on [Webhooks](/docs/api/webhooks). Connecting Gmail, Microsoft 365 or a calendar stores an OAuth grant, never a password, and disconnecting removes it.

### Sign in

Accounts sign in with an email and password, or with Google or Microsoft where enabled. Passwords are hashed by the authentication provider. The session lives in a cookie and is checked again on the server for every request.

## AI data handling

URL: https://kabaido.ai/docs/security/ai-data-handling

Know what the AI sees, what it never does and how the homepage AI is kept apart from your data.

Why: An AI that reads your enquiries holds the commercially sensitive core of your business.
What: One provider, no training, cited values and deterministic pricing.
How: The AI reads and ranks; your own catalogue, formulas and rules price.

### One provider, no training

Kabaido's AI runs on Anthropic models only. [Anthropic's commercial terms](https://www.anthropic.com/legal/commercial-terms) bar training its models on customer content, and Kabaido does not train on your data either. No other AI vendor receives it.

### What is sent, and what is not

| Sent with a request | Never sent |
| --- | --- |
| The document being read: text, tables, scanned pages | Your whole catalogue |
| Your units, currency and schema field names, with example values from a sample of your products | A price, a cost or a margin |
| The relevant knowledge packs and a short outline of your workspace setup | Your customer list, or a contact's email or phone |

Catalogue search and matching run inside the platform, on the database. Making your catalogue searchable sends no product data to the AI provider.

### Cite or abstain

Every extracted value records where in your document it came from. A value the source does not state stays empty and raises a clarification. Fit scores, match bands, prices and engine calculations are deterministic code, so the same enquiry on the same catalogue gives the same answer tomorrow.

### The homepage AI

- The domain box on the Kabaido homepage runs on its own capped key, separate from the one that serves workspaces, with a daily spend cap and a switch to turn it off.
- It reads only a public website: the home page and at most a few linked pages. It touches no organisation and no workspace data.
- It keeps each domain's answer for 30 days, stores a visitor's address only as a salted hash and is rate limited per visitor and overall.

### Spend protection

Every AI call is recorded with its model and cost. The month's usage, an optional [daily budget](/docs/billing/daily-budgets) and per organisation rate limits stop a runaway document or a looping integration.

## Compliance and GDPR

URL: https://kabaido.ai/docs/security/compliance-and-gdpr

Find the legal frame, the sub-processors and where they run, and how to exercise data rights.

Why: You decide what goes into the platform, so you need to know who processes it and where.
What: UK GDPR roles, the named sub-processors, data residency and your rights.
How: Kabaido processes on your instructions only; the legal pages carry the binding text.

### Controller and processor

Kabaido is a UK service under UK GDPR and the Data Protection Act 2018. For the business data you load you are the controller and Kabaido the processor. We do not mine your catalogue, train on your quotes or build a dataset from what passes through.

### Sub-processors

Kabaido uses five sub-processors, named in the data processing agreement: Supabase, Vercel, Stripe, Resend and Anthropic.

| Provider | For | Where |
| --- | --- | --- |
| Supabase | the database and storage | EU: AWS Frankfurt (eu-central-1) |
| Vercel | hosting | UK: London |
| Stripe | payments | [The provider's security page](https://docs.stripe.com/security) |
| Resend | email | [The provider's security page](https://resend.com/security) |
| Anthropic | AI | [The provider's security page](https://trust.anthropic.com) |

Only when you use them: Google for Gmail inbox sync; Microsoft for Microsoft 365 inbox sync. Meetings run on Google Meet and Kabaido keeps no recording.

We do not sell data and run no advertising trackers. Cookies are essential only.

### Your rights

Access, correction, erasure, restriction, portability and objection are honoured: email hello@kabaido.com. You can also raise a concern with the ICO. If one of your own customers asks what you hold, you answer, and [the export tools](/docs/security/data-export-and-deletion) exist so you can.

### The legal pages

- [Privacy policy](/legal/privacy)
- [Data processing agreement](/legal/dpa), with a countersignable copy on request
- [Terms of service](/legal/terms)
- [Acceptable use](/legal/aup)
- [Cookies](/legal/cookies)

> The certifications on [the security page](/security) are each provider's own, as its security page states them, linked so you can check.

## Platform and payment security

URL: https://kabaido.ai/docs/security/platform-and-payment-security

See the guards on the public surfaces: payments, rate limits, browser headers and assistant connections.

Why: Every public door is a place to be scanned, flooded or framed.
What: Stripe for cards, database backed rate limits, strict headers and scoped connections for AI assistants.
How: Each guard applies on every route, not only the pages that feel sensitive.

### Payments

Card details go straight to Stripe. Kabaido stores only Stripe's references, the plan, the billing period and the renewal date, and accepts payment events only with a valid Stripe signature.

### Rate limits

The REST API, the AI routes, inbound endpoints, the quote portal, access code redemption and the OAuth endpoints are rate limited. The limiter is a token bucket held in the database, so it holds across every server, lets a legitimate burst through and stops a sustained flood with a clear error. Limits per surface are on [Rate limits](/docs/api/rate-limits).

### Browser headers

| Header | What it does |
| --- | --- |
| Strict-Transport-Security | Two years, subdomains included, preload requested: no plain HTTP. |
| X-Frame-Options and frame-ancestors | Framing denied everywhere except the wizard embed, which is protected by its key and a domains allowlist. |
| X-Content-Type-Options | No MIME sniffing, so an upload cannot run as something else. |
| Referrer-Policy | Strict origin when cross origin, so a token link never leaks to another site. |
| Permissions-Policy | Camera, microphone and geolocation are locked down on every route. |
| Content-Security-Policy | Report only while violations are observed on real traffic, with every allowed origin named. |

### AI assistant connections

MCP connections are approved by you over OAuth with PKCE, carry scopes capped by your own role and can be revoked from Settings. Access tokens are short lived; a call outside the granted scopes returns an error, not data.

### Reporting a vulnerability

Email hello@kabaido.com with the details and a person reads it. Please never test against another organisation's data.

## Data export and deletion

URL: https://kabaido.ai/docs/security/data-export-and-deletion

Take a copy of your data whenever you want and delete it when you leave.

Why: Your data is yours, on every plan, including after you leave.
What: An export on every list, a full export on request and deletion by the owner.
How: Export from the list you are looking at, or email for everything; delete from Organisation settings.

### Export a list

1. Open a list such as `/app/quotes`, `/app/orders` or `/app/customers` and filter it to what you want.
2. Choose **Export**, then pick the rows (**Filtered**, or **Shown** when nothing is filtered, or **Everything loaded**), the columns and the file name.
3. Choose CSV or JSON and **Download**.

> Export is on every plan, free included, and never charged.

### Full export

Email hello@kabaido.com for everything: one CSV per table, covering requests, quotes, orders, customers, the catalogue, servicing, configurators, usage and emails. API key hashes and integration credentials are redacted and never leave the database.

### Delete the organisation

1. As the owner, open `/app/settings/organisation` and scroll to **Danger zone**.
2. Choose **Delete organisation**, type the confirmation shown and choose **Delete forever**.

Or email hello@kabaido.com and we delete it for you. Invoices and the accounting records the law requires are kept only as long as it requires; your catalogue, customers, quotes and requests are not kept.

Removing a colleague under `/app/settings/users` revokes their access at once but keeps the records they created, which are your organisation's.

> Deletion cannot be undone. Take an export first.

## The customer facing trust boundary

URL: https://kabaido.ai/docs/security/the-customer-facing-trust-boundary

Know why a customer signed in to your Commerce surface can see their own records and nothing else.

Why: Letting customers sign in is only safe if a customer can never read another customer's rows or your costs.
What: A separate kind of user, a customer, that is never a member of your organisation.
How: Each table a customer may read has its own customer policy, every other table returns nothing, and an access code is the only way in.

### The rules the database enforces

| Rule | What it means |
| --- | --- |
| Never a member | A customer has no membership row, so every member check in the database is false for them by construction. |
| Zero rows elsewhere | A customer reads nothing from any table outside a short allow list. A test walks every table in the schema as four customers and expects zero rows, so a table added later is covered without anyone remembering. |
| Their own rows only | Customer A never sees customer B's rows, in the same organisation or another. |
| No internal columns | Cost, internal notes, storage paths and approval tokens are reached only through views that leave them out. |
| Read under the database's rules | The customer surface queries as the signed in customer, never with elevated access, so application code cannot widen what a customer sees. |

### The only way in

- Each customer record gets an access code, issued by you. Redeeming it links the signed in person to that customer and nothing more.
- Codes are long and random, and redemption is rate limited by address, by account and by organisation. A code that does not work always gets the same answer, so a guess learns nothing.
- A session is bound to one host: signing in on one supplier's address gives no session on another's.
- Nobody can create a workspace from a customer address.

> Switching Commerce off makes the whole surface unreachable at the database, with every row kept. The customer AI is off until you switch it on and is pinned to the same rows.

# Docs: Changelog

## From your request, on every design card

URL: https://kabaido.ai/docs/changelog/2026-10-22-from-your-request

A design card shows which values the buyer stated, apart from those the selector chose.

Values the buyer wrote in the request now carry a From your request chip on the design card, with the words they came from. Values the selector chose from published data keep Selector set, and values read from a DXF keep From the DXF.

## A cutter asked for, never a drill offered

URL: https://kabaido.ai/docs/changelog/2026-10-22-milling-cutter-not-drill

A request for a milling cutter is never offered a drill, reamer or tap as one of its choices.

When the customer asks for an end mill or a Fräser by size alone, the tools offered are milling cutters. A drill of the same diameter no longer appears among the choices.

## Every pick on a request is kept

URL: https://kabaido.ai/docs/changelog/2026-10-22-picks-on-two-lines

Choosing a tool on several lines of one request in quick succession keeps every choice on the quote.

When two lines of a request each asked you to pick a tool and you picked both within a second or two, the first pick could be lost and its line reach the quote unpriced. Picks now save one after another and none is overwritten.

## Asked for a long tool, offered long tools

URL: https://kabaido.ai/docs/changelog/2026-10-22-long-tool-asked

A request for a long or long reach tool with no reach stated is offered the long tools first and never sold the standard one.

When a customer asks for a long ball nose, a long reach or a tool for a deep cavity without giving the reach, the tools in your range with a long neck or reach lead the card, and the standard length tool is never selected for them. Give the reach and it is matched as usual.

## German finishing and the right tool

URL: https://kabaido.ai/docs/changelog/2026-10-22-german-finishing-and-the-right-tool-for-the-job

A German enquiry that names a finishing pass gets tools chosen for it, and a card full of stock that suits the job badly now shows the one that suits it.

Schlichten von Rippen, Wände schlichten and the other German words for a finishing pass on walls, ribs and webs are read as a profile job, so the flutes, helix and coating are chosen for it instead of the general row.

When every stock tool on a review card goes against the application, the tool in your range that suits the job better is offered beside them, with the length it differs on shown on its chip. It is never selected for you.

A step drill drawn in a DXF no longer asks which of its own diameters is the cutting one: the drawing answers it.

## PCD shank tools price the whole job

URL: https://kabaido.ai/docs/changelog/2026-10-22-pcd-shank-guide-pricing

A PCD shank tool's price now covers every operation, the braze and a margin at guide rates you replace with your own.

Every operation of a PCD shank tool is priced at a guide rate, with the braze, the flux and a 30 per cent margin, so a quote shows a price from the first design. Each figure is a sample you edit on the rates screen, and your own Costing settings rates cost the work once you set them.

Long cutting rows are built of several plates, as the makers build them, a compression router has a notch at its up cut length, and 0.8 and 1.0 mm blanks suit small end mills. The guide prices for discs, bar, carbide rod and braze were checked against suppliers on 22 October.

## PCD shank tools take the inputs buyers specify

URL: https://kabaido.ai/docs/changelog/2026-10-22-pcd-shank-buyer-inputs

Set the hand, the cut direction, a compression router's up cut length, the shank clamping length, both clearances and a corner radius, and the drawing states them as a buyer reads them.

A compression router now cuts up to its up cut length (lpos) and down above it, as the makers build them, and the drawing gives the minimum depth of cut. The shank clamping length is checked against the EN 847-2 minimum, and a g6 shank joins h6 and h5.

The solid's sections are clean curves: the rake wall on the plate's face, a radiused floor, a relieved land and a run out that stays clear of the clamp. A left hand tool is drawn as its mirror, and the drawing reads Z as cutting and plunge, Z 2+1.

## PCD shank tools cost each machine at its own rate

URL: https://kabaido.ai/docs/changelog/2026-10-22-pcd-shank-rates-and-solid

Each operation of a PCD shank tool is costed at its own station's rate, and the solid shows open flutes and helical wings as real tools have.

Set a machine rate on each station and every operation of a PCD shank tool is costed at it: sawing, tip cutting, edge erosion and the rest no longer share one rate. Two station groups join the list for it, bar sawing and tip cutting.

The cutting list chooses the cheapest disc that holds the tips, the cost parts add up to the total, and the routed minutes read as your own once you save your rates. The solid now shows an open flute in front of every PCD face, a relieved land behind it and, on compression and multi tip routers, the plates on helical wings.

## PCD shank tool braze follows the data sheet

URL: https://kabaido.ai/docs/changelog/2026-10-22-pcd-shank-accuracy

The PCD shank tool's braze grams and cost now follow the data sheet's own rule.

An accuracy check against three worked jobs found the braze allowance a tenth too high, so each tip now takes the seat times the braze gap and fillet the data sheet gives.

## Design stock rows load cleanly

URL: https://kabaido.ai/docs/changelog/2026-10-22

New design modules load their stock rows in one pass.

Every shipped stock row now states whether the bar is prepped, so a new design module seeds in one pass.

## The PCD shank tool joins Design Engineer

URL: https://kabaido.ai/docs/changelog/2026-10-21-pcd-shank-tool

Design a PCD tipped router, end mill, drill or reamer, and its bar and discs are reserved when the order is made.

Design Engineer gains the PCD shank tool: straight and shear routers and end mills with brazed PCD tips, a real disc nest, true cost, a drawing, STEP and the nest DXF.

A designed PCD shank line now reserves its bar and discs when the order is made and uses them up when it is done. Shank prep and the braze reach Machinist with the setup minutes from your routing.

## A wider chip space for design modules

URL: https://kabaido.ai/docs/changelog/2026-10-21-design-chip-space

Tool chip spaces open wide with a radiused root and tip tables stack in the rail, none of it switched on yet.

Tool chip spaces open wide with a radiused root and tip tables stack in the rail, none of it switched on yet.

## Tool finishes and a nest DXF for design modules

URL: https://kabaido.ai/docs/changelog/2026-10-21-design-finishes

Steel, diamond and braze draw as their own finishes, nests export to a cutting DXF, and Stock mode groups lines by family, none of it switched on yet.

Steel, diamond and braze draw as their own finishes, nests export to a cutting DXF, and Stock mode groups lines by family, none of it switched on yet.

## The PCD shank tool's model, nest and take-off

URL: https://kabaido.ai/docs/changelog/2026-10-21

The PCD shank tool's model, nest and take-off, not yet switched on.

The PCD shank tool's model, nest and take-off, not yet switched on.

## Design quotes build on what your stock costs you

URL: https://kabaido.ai/docs/changelog/2026-10-20-design-stock-cost

A designed tool prices its PCD discs from the disc you hold, at what it costs you, and says so when it has to use your rate instead.

Each stock row in Design Engineer now holds its cost beside its price, typed in the stock dialog or carried in a cost column on a CSV import. A design that uses two kinds of stock, such as a saw blade's steel body and its PCD disc, matches both, and the materials panel lists each under its own heading.

The disc line on a PCD saw blade or profile cutter now prices from the matched disc row's cost and names its code. Where no disc you hold carries a cost, the quote uses your disc price rate and the cutting list says the figure is modelled.

## Repeat orders score every detail of the last order

URL: https://kabaido.ai/docs/changelog/2026-10-20-repeat-order-scoring

Every detail a repeat order takes from the earlier order now counts towards which tool it matches.

A detail filled from the customer's earlier order, such as through coolant, now decides between two tools that differ only in it, so the tool they bought before is offered first.

## German RFQs read as their engineers wrote them

URL: https://kabaido.ai/docs/changelog/2026-10-20-german-cutting-words

A German enquiry is read the way its engineer wrote it: the corner radius, the neck and the finishing pass stay what they were.

The structured request now reads the German words for a corner radius, the flutes and lengths, a relieved neck and its reach, internal coolant and roughing, semi-finishing and finishing. An end mill with a corner radius is no longer listed as square with a question about its end.

## Repeat orders take the details of the last order

URL: https://kabaido.ai/docs/changelog/2026-10-20-repeat-order-history

A customer who asks for the same tool as last time gets it, with each detail cited to their earlier order.

When a repeat request leaves details out, every detail the customer's earlier order holds for that tool is now taken from it: the coating and the coolant as well as the flutes and the end. Each one says which order it came from and can be changed on the line. Anything the customer states still wins.

## Orders keep their customer, and repeats read past orders

URL: https://kabaido.ai/docs/changelog/2026-10-20-customer-context-orders

An order raised for a pinned customer keeps that customer and their prices, and a repeat order fills its gaps from what they bought before.

Create order now raises the order for the customer the order card shows, so their terms, price breaks and reference stay on it. When a customer asks for the same tool as last time without restating it, the details they left out are filled from the tools on their earlier orders and accepted quotes, and each one names the order it came from.

## No made to order note under a priced design

URL: https://kabaido.ai/docs/changelog/2026-10-20-designed-line-nudge

A special the Design Engineer has priced no longer carries a note saying nothing is priced.

The made to order note now appears only for lines nothing has answered. A line set out and priced by the Design Engineer in the same answer no longer shows it.

## Near miss specials are designed and priced

URL: https://kabaido.ai/docs/changelog/2026-10-20-special-near-miss

A special endmill the range only nearly holds is designed and priced, from the words the customer wrote.

When every catalogue tool that comes close misses a size the customer gave, such as a 120 mm overall length against tools of 104 mm, the request no longer asks you to pick one of them: the Design Engineer sets out the tool asked for and prices it in the same answer. A tool that meets every stated size is still offered first. The design also reads the customer's own line, so the card quotes what they wrote, in their language.

## German special enquiries keep their neck and coolant

URL: https://kabaido.ai/docs/changelog/2026-10-20-german-tool-words

A special tool asked for in German keeps its neck, its reach and its internal coolant.

Design Engineer now reads the words a German enquiry uses for a necked tool and its reach (Ausspannlänge, Halslänge, freigeschliffen auf) and for internal coolant (innere Kühlung, IK, IKZ), so the special is set out as the same line in English would be. "Ohne IK" is read as no coolant through the tool, and 1.2343 is read as a hot work tool steel.

## Customer drawings download on the live site

URL: https://kabaido.ai/docs/changelog/2026-10-20-customer-drawing-download

The customer drawing for a carbide endmill now downloads from kabaido.ai.

A fix for the customer drawing: the download failed on the live site because the solid could not be built there. It builds now, and the sheet is the one described in the 1.22.16 and 1.23.16 notes.

## Cleaner customer drawings

URL: https://kabaido.ai/docs/changelog/2026-10-20-customer-drawing-labels

Every label on a customer drawing sits clear of the lines and reads on any brand colour.

The end form note and the section marks no longer touch the dimension lines, and the view titles and the rule under the title block stay legible on a very light brand colour.

## Customer drawings for carbide endmills

URL: https://kabaido.ai/docs/changelog/2026-10-19-customer-drawing

A carbide endmill designed in Design Engineer downloads as one sheet a customer approves and a grinder makes from.

Documents and exports now offers a customer drawing for the carbide endmill: the side view at a true scale with every length, diameter and shank fit, the flute section, the land and the end tooth, three views of the solid, the tool data, and the customer with their own prices at each quantity, all on one A4 sheet with your logo and brand colour. A works copy carries the rod and grinding time instead of prices.

## One setup offer, said the same everywhere

URL: https://kabaido.ai/docs/changelog/2026-10-17-live-site-audit

Every page says the setup offer, the plans and what each product does the same way.

The setup offer now reads the same on the homepage, pricing, how it works and the FAQ: included on a paid plan started by 31 December. Machinist names tool grinding among its machine modules, and page titles and link previews are tidier.

## The cutting tools page names every product a tool maker uses

URL: https://kabaido.ai/docs/changelog/2026-10-17-cutting-tools-every-product

A cutting tool maker sees grinding and regrinds among the products that apply to them.

The cutting tools page now lists Machinist, which raises the grinding order from each designed tool, and Service Centre, which tracks every regrind under the tool's own code, beside Sales Engineer, Design Engineer, Stock and Wizard.

## Booking and sign up say what you get

URL: https://kabaido.ai/docs/changelog/2026-10-17-routes-in

The walkthrough and sign up say what each gives you, and machine knives are read as the catalogue lines they are.

Booking a walkthrough now says it is 30 minutes on your own job and invites an RFQ or a drawing. Sign up says the workspace is yours and your geometry and data stay yours, with a walkthrough on offer instead.

Requests read machine knives as catalogue lines, and a form cutter drawn from a DXF shows which values came from the drawing and which the engine chose. A new guide walks through quoting a special endmill from the first email to the quote.

## Step drills read right, and every trade page shows the work

URL: https://kabaido.ai/docs/changelog/2026-10-17-step-drills-trade-pages

A step drill's pilot and step are read as two sizes, and each trade page shows the product working before it asks for anything.

Requests read a step drill's pilot and step as separate sizes, keep a holder's hand and a wheel's grit in the form the catalogue holds, and send a regrind line to cutting rather than coatings. Spec sheets and other documents print bold text in bold again.

The cutting tool, tool servicing, woodworking and sawing pages show live previews of the product at work, and the product and pricing pages open on what each one does with a real screen beside it.

## Cutting tool makers start where their work starts

URL: https://kabaido.ai/docs/changelog/2026-10-17

A cutting tool maker signs up to the endmill design module, a first run that leads and spec sheets that export.

Onboarding has Cutting tool manufacture and Subcontract machining as trades, and each trade starts with the modules its work runs through. The app home now follows the trade, shows the next setup steps until the first request and offers one example that fits the workspace.

Design Engineer spec sheets export as PDF again, with prices in the quote's currency. Matching keeps a request to products of its own kind, and a request that states mild steel at a hardened steel hardness now asks which it is instead of guessing.

## Designed lines priced on the first request

URL: https://kabaido.ai/docs/changelog/2026-10-13-design-pricing-retry

Every special in a request is priced, including the first request after an update.

A request with several specials could leave some of them unpriced when it was the first one after an update. The price calculation now has more time to start, so each designed line carries its price.

## Designed specials take the customer's terms

URL: https://kabaido.ai/docs/changelog/2026-10-13-designed-lines-customer-terms

A special designed in an answer goes onto the quote at the customer's own price.

When a request's special is designed and priced in the answer, the quote now applies the pinned customer's discount to it, as it does to catalogue lines. Change the quote's customer and the line reprices with it.

## Special endmills on an RFQ are designed

URL: https://kabaido.ai/docs/changelog/2026-10-13-special-endmill-lines

Each special endmill on a request for quotation is designed and priced in the same answer, however the customer words it.

A line such as "12 mm 4 flute end mill, R1.5 corner radius, necked for 45 mm reach" is now set out by the Design Engineer inside the answer, with its price on the quote draft. It used to need the words "special" or "custom" before it was designed.

## Chamfer mills read from the words

URL: https://kabaido.ai/docs/changelog/2026-10-13-chamfer-mills

A chamfer mill asked for in words is set out as a chamfer, and a form cutter keeps its job when its profile has a chamfer.

Ask for a "10 mm 90 degree chamfer mill" and the Design Engineer now sets out a chamfer: the angle and the tip from your words, and the cutting length from the cone. When an angle could mean the included angle or each side, it asks.

A form cutter sent with its DXF whose profile includes a chamfer now gets its flutes, helix and coating chosen for the job, as any other form cutter does.

## Quote history shows the right time

URL: https://kabaido.ai/docs/changelog/2026-10-09-quote-history-times

The times in a quote's history are the same wherever the page is shown.

The times in a quote's and an order's history now always read in UK time. Before, the page could briefly show one hour and then correct itself, which logged an error in the browser.

## Terms on the closing slide

URL: https://kabaido.ai/docs/changelog/2026-10-09-presentation-terms

A presentation can state its plan and what setup covers under the closing decisions.

The closing slide of a presentation can now carry one short paragraph under the decisions, for the plan and what setup covers.

## A prepared email knows the customer

URL: https://kabaido.ai/docs/changelog/2026-10-09-prepared-email-knows-the-customer

An email you prepare and send later is priced for the customer who sent it.

When the inbox prepares an enquiry for you to send later, the request now carries the customer who sent it, so their special prices and terms are on the draft and the quote.

## Email matches your whole catalogue

URL: https://kabaido.ai/docs/changelog/2026-10-09-email-matches-your-catalogue

Enquiries that arrive by email are matched against your catalogue at any size.

An enquiry that arrives in a connected inbox is now matched against your catalogue whatever its size, with the same results as one pasted into the app. Before, a catalogue of more than 50 products found no matches for the email agent.

## Price these, by email

URL: https://kabaido.ai/docs/changelog/2026-10-09-price-these-by-email

An email asking you to price a list of items opens as a request for quotation.

An email that asks you to price these, followed by a list with quantities, is now read as a request for quotation, even when it is worded as a question. Before, it could be answered as a technical question.

## The pinned customer on the quote

URL: https://kabaido.ai/docs/changelog/2026-10-09-pinned-customer-on-the-quote

Pin a customer on a request and the quote made from it is theirs, at their prices.

A request with a customer pinned now makes a quote for that customer, so their special prices and terms are on the draft and on the quote it creates. A company named in the request that you hold still takes priority.

## Either or in a request

URL: https://kabaido.ai/docs/changelog/2026-10-09-either-or-flutes

Ask for 4 or 5 flutes and every tool in the range that fits either is matched.

When a request offers a choice of numbers, such as 4 or 5 flutes, a tool that has either is now a match. Before, the choice was read as one unknown value and the line found nothing.

## A form cutter from your DXF

URL: https://kabaido.ai/docs/changelog/2026-10-08-form-cutter-from-dxf

Send a form cutter enquiry with its DXF and the tool opens in the design module ground to the file, drawn and priced.

Attach the DXF of a form cutter's section to an endmill enquiry and the form, the cutting diameter and the length of cut are taken from the file, each marked From the DXF. The flutes, helix, coating and coolant blank are chosen for the material from published data, and the tool is drawn and priced on your own rates. No AI reads the file, and it works in a workspace that also holds a catalogue.

Arcs in an imported DXF are now drawn exactly as the file defines them, and a drawn profile keeps its dimensions to the micron. Saving or exporting a design from an AI answer keeps a drawn form.

Requests are now read by Claude Haiku 5.5, a newer and faster model, with harder requests still passed to Claude Sonnet 5.5.

## The endmill config email and its usage boost

URL: https://kabaido.ai/docs/changelog/2026-10-06-endmill-config-email

Accounts that tried the endmill config can try it again with extra usage.

Accounts that sent a custom endmill request, and tool makers with a Kabaido account, were given extra usage and had the endmill config switched on, so they can try it again with different tools. Nothing changes for other accounts.

## Custom endmill requests open in the design module

URL: https://kabaido.ai/docs/changelog/2026-10-05-custom-endmill-requests

Type a custom solid carbide endmill into the AI and it opens in the design module with the sizes you wrote, and the free plan no longer stops a first request.

A custom endmill typed into the AI is read straight into a specification with no model call: the diameter, flutes, corner radius, flute and overall length, shank, coating, end form and hand you wrote, each kept exactly as written and opened in the endmill design module with the material's published flutes, helix and coating where you gave a material. It reads the shorthand tool makers use (Ø10 z4 r0.5, 10x22x72) and the words in English, German, French, Spanish, Italian, Portuguese, Czech, Polish and Turkish. Sizes written in inches are read as inches and the answer says so.

When a request says two things about one size, such as two overall lengths, a 10 mm or a 12 mm tool, or coated and uncoated, it asks which one instead of choosing. A length that belongs to the part (a 120 mm long plate) is never taken for the tool.

A first request on the free plan no longer stops before it answers: the limit on a single request was set below the cost of reading Kabaido's own instructions, so a cold request was cut off. The free allowance itself does not change.

## Quote and Send take you to the record

URL: https://kabaido.ai/docs/changelog/2026-10-05-e2m-walk-fixes

Quote a designed endmill and the button becomes Open quote; send it to the factory and the Machinist order opens.

Quoting a tool in Make it no longer closes the panel: the Quote button turns into Open quote, and Send to the factory turns into Open factory order and takes you to the order in Machinist. Quote rows open from anywhere on the row, quote and order lines link back to their design, and the factory order links back to its quote and design.

## A saved design is always priced

URL: https://kabaido.ai/docs/changelog/2026-10-05-e2m-quote-worker

A design saved from the workbench keeps its price, so the quote made from it carries the price too.

The price calculation on the server now allows three seconds instead of one, so a design saved right after a quiet spell is no longer stored without a price.

## A designed endmill goes to the grinder

URL: https://kabaido.ai/docs/changelog/2026-10-05-e2m-enquiry-to-machine

Send a quoted solid carbide endmill from Design Engineer to a tool grinding order in Machinist, with the rod, wheels and fluid kept in Stock.

A machining enquiry in the AI interface is now read by the machining selector into an endmill specification, with each choice cited and no model call when the words are enough. Design Engineer gains a **Make it** panel for the endmill: the rod, the wheel set, the machine and the process, planned from your own stock. A saved design can be quoted and sent to the factory.

Machinist gains a **Tool grinding** machine module, installed by the Solid carbide tool making preset: each grinder's wheel pack drawn to scale, a printable factory order, and the grind section by section. Stock gains categories for products, rod and material, tooling and fluids, an item's wheel or fluid specification and an On machines view. The grinder's own software still sets the wheel path.

## Introductions carry a signature

URL: https://kabaido.ai/docs/changelog/2026-10-05-sequence-signature

Nothing changes in your workspace: the introductions Kabaido sends now end with the sender's own signature.

The emails Kabaido sends to introduce itself now close with the sender's name, role and contact details, the same as a hand written message. Your workspace, your data and every product work exactly as before.

## Our internal tools moved

URL: https://kabaido.ai/docs/changelog/2026-10-05

Nothing changes in your workspace: the console our own team uses now runs outside the platform.

The console Kabaido uses to run its own operations now lives in a separate app. Your workspace, your data and every product work exactly as before.

## Opt out stops every follow up

URL: https://kabaido.ai/docs/changelog/2026-10-02-q4-sequence-sender

One click on the opt out link in an email from Kabaido now ends the follow ups to that address as well as the first email.

Emails from Kabaido that follow up on an earlier message carry the same opt out line and privacy link as the first one, and one click stops anything further being sent to that address. A reply from anyone at your company also stops the rest of the follow ups.

## Clearer answers from the customer assistant

URL: https://kabaido.ai/docs/changelog/2026-10-02

The customer assistant now knows how much each list shows and says plainly that deliveries are not recorded yet.

The assistant on a customer account reads quotes, orders, items and documents with their limits stated, so it can say when a list may hold more. It tells a customer that no deliveries are recorded yet instead of implying there are none to find. The homepage answer and the enquiry reply no longer carry fixed word counts.

## Setup included until 31 December

URL: https://kabaido.ai/docs/changelog/2026-09-29-q4-setup-included

Start a paid plan before the end of the year and setup costs nothing, and the site now answers who it is for and how to check it first.

29 September 2026.

- Setup is included for any business that starts a paid plan before 31 December 2026: your catalogue, prices and customers imported, your inbox and systems connected and one design, wizard or machine module built. Settings, Billing shows the offer and books your setup call after checkout.
- The homepage opens on where most commercial offices are today, then why Kabaido exists, a door each for tool servicing, cutting tool makers and distributors, and the facts you can check for yourself.
- The tool servicing, cutting tools, distribution, surface treatment, woodworking tooling and sawing pages show what changes step by step, the products that apply and one small ask: send us one job.
- A funding section covers Made Smarter in every English region and Help to Grow: Management, checked on each official page.
- Pricing says which plan fits which business, and that no VAT is charged. Every Start free button says no card.

## Every stated value is what the customer wrote

URL: https://kabaido.ai/docs/changelog/2026-09-29-aei-cite-what-was-written

AEI now files a value as stated only when the customer wrote it, and asks which one they meant when a request names a family but not the grade.

29 September 2026.

- When a request says "bimetal" and your catalogue sells bimetal M42 and bimetal M51, AEI asks which one rather than choosing a grade for the customer.
- The workpiece group recommended for a cutting tool follows the material and the hardness the request states. A hardened steel group is only recommended when the request says hardened or states the hardness.
- A line with no price in the request no longer shows an empty price field.
- What each request uses from your plan is unchanged.

## Harder requests read by a stronger model

URL: https://kabaido.ai/docs/changelog/2026-09-28-harder-requests

The requests AEI hands to its stronger model now go to a newer one, with no change to what a request uses from your plan.

28 September 2026.

- A long, mixed or hard to read request, and a match you challenge, is now read by a newer and more capable model.
- What each request uses from your plan is unchanged.

## Every page says exactly what it does

URL: https://kabaido.ai/docs/changelog/2026-09-28-says-what-it-does

Every product description says exactly what the product does, delivery states follow the real path, and a customer's approval shows on the item's history.

28 September 2026.

- Wizard lists all four wizards, machining tools included. A run on your customer surface arrives as a quote request; a wizard on your own website records every run in Activity.
- Design Engineer lists solid carbide endmills among what it configures, and Stock lists only the movements the ledger records today.
- A delivery moves only along its real path, and an attempt to skip a step says which step it came from and which it tried to reach.
- When your customer approves or declines a price change, the answer is recorded on the item's history with everything else that happened to it.
- Coated fasteners ordered by a count read as goods to a stockist, and a finisher that stocks none is offered the coating on the customer's own parts.

## Fastener sizes read as thread and length

URL: https://kabaido.ai/docs/changelog/2026-09-28-fastener-sizes-read-whole

A bolt asked for as M10 x 40 is read as an M10 thread 40 mm long, so it matches your catalogue the way you list it.

28 September 2026.

- A fastener written as one size, such as M10 x 40 or M10 x 1.5 x 40, is read as the thread and the length separately, the way catalogues hold them.
- A thread with only its pitch, such as M8 x 1.25, stays as written.

## Nottinghamshire in Inspect

URL: https://kabaido.ai/docs/changelog/2026-09-28-nottinghamshire-county

Inspect now covers Nottinghamshire: 3,617 manufacturers recorded across its eight local authorities, 571 of them with verified information.

28 September 2026.

- Nottinghamshire joins Derbyshire and South Yorkshire as a live region in Inspect, with Nottingham, Broxtowe, Gedling, Rushcliffe, Ashfield, Mansfield, Newark and Sherwood, and Bassetlaw.
- 3,617 manufacturers are recorded against the 2,365 manufacturing sites the ONS counts in the county, and 571 carry verified information from their own websites and filed accounts.
- Every profile was checked against the pages it cites before it went live, and anything the evidence did not support was taken out.

## AEI reads more of what your customer wrote

URL: https://kabaido.ai/docs/changelog/2026-09-28-aei-reads-more-of-what-was-written

The AI reads quantities, part numbers, sizes and refusals the way your customer wrote them, in any of the ten languages, and sends each question in /app to the right place.

28 September 2026.

- A quantity your customer states is always read as theirs, wherever it sits in the line: 20 off, x20, 20 pcs, 1,000 Stück or twenty. A size such as M10 x 40 is never taken for the quantity, and an estimate such as around 10 is asked about rather than guessed.
- Purchase order, invoice and quote numbers are never read as part numbers, and manufacturers' own codes are kept as written.
- Bearing, belt, thread and welding designations such as 6204-2RS, SPZ 1250 and M8x1.25 bring the right engineering knowledge to the request.
- An option your customer refuses, such as without topcoat or sans revêtement, stays refused in every language.
- Questions in /app go to the right place: a technical question is no longer mistaken for a help request or a record lookup, and a part number is no longer read as a serial.
- Ordinary business emails with delivery or handling instructions are no longer refused, while attempts to instruct the AI still are.

## Every page shows the real interface

URL: https://kabaido.ai/docs/changelog/2026-09-28-interfaces-you-can-see

Every product and platform page on the website now shows the screens you would actually use, with a short walkthrough and 3D views of Wizard and Design Engineer answers.

28 September 2026.

- Each product page opens a See it working walkthrough: three or four real screens in order, from the request arriving to the result your customer sees.
- Every row under In more detail shows the part of the platform it describes, with its data labelled as live, from a real test file or demonstration data.
- Wizard and Design Engineer show their answers in 3D, rendered from the same engines the platform runs.
- Area, part and industry pages show what each part of Kabaido looks like with your products switched on.
- Destructive buttons in the platform's dark theme are easier to read.
- The AEI figures on the homepage move more slowly so each one can be read.

## Certified foundations

URL: https://kabaido.ai/docs/changelog/2026-09-28-certified-foundations

See the certifications Kabaido runs on, on the homepage, the security page and the FAQ.

Every provider under Kabaido holds SOC 2 Type II; the database, hosting and AI hold ISO 27001 and payments run on PCI Level 1. [The security page](/security) links each provider's own page so you can check.

## Asked once, sent by name

URL: https://kabaido.ai/docs/changelog/2026-09-28-asked-once-sent-by-name

The AI never asks whether a customer wants what they asked for, and an order's history names who sent each delivery and how.

28 September 2026.

- A request to regrind and recoat is taken as a yes to the coating, so the only question left is which coating.
- An order's history says how each delivery left, on which run or with which carrier, under the name of the driver or the person who booked it.
- Design Engineer's price panel reads small rates to the penny, such as £0.75 per minute, and keeps the tenth of a penny only where it matters.
- Your customers' coming deliveries are read on the UK day, so a delivery from yesterday never shows as coming up just after midnight.

## Answers that add up, everywhere

URL: https://kabaido.ai/docs/changelog/2026-09-27-answers-that-add-up

The quote draft shows the prices the quote will carry, the AI matches what the request and its application settle, and every screen says what is true.

27 September 2026.

- The quote draft prices every line with the customer's own prices and your quantity breaks, exactly as the quote it creates. Picking a product for a line prices it on the card straight away.
- Where the request and its application settle the product, the AI matches it outright, and a product that goes against something the customer stated or against the recommendation says so on its card.
- A quantity nobody stated is marked as assumed, a line's description says only what the customer said, and a figure already in the request is never asked for again.
- Design Engineer's price panel always adds up to its total, with any price break shown as its own line, and number fields settle before they reprice.
- Service Centre queues count each tool once, at the bench it is waiting for, and a tool is completed only when its benches are done.
- Route puts a day's drops in a sensible order round the promised windows, and departing the van dispatches what it carries.
- Machinist, Wizard, Stock, Source, quotes, orders and your customers' own pages read their figures in words and units, with history that shows every step.

## Calmer text fields and clearer approvals

URL: https://kabaido.ai/docs/changelog/2026-09-25-calmer-fields-clearer-approvals

Text fields no longer flash blue when you select them, and a customer approving a price change reads every measurement by its name.

25 September 2026.

- Selecting a text field shows the cursor and a calm grey border instead of a blue ring, so nothing flickers as you click. Buttons, links and checkboxes still show a clear ring when you move through them with the keyboard.
- The price change approval your customer opens, and the email that links to it, lists each measurement by its name with its unit, such as Diameter 16 mm or Regrind OD only, instead of the code behind it.
- An item's History in Service Centre names the station or the person for each scan and never shows an internal id.
- The website's homepage shows the AI at work on a real request, a live strip of what Application Engineering Intelligence knows and has done, and a clearer view of each product.

## Website analytics count real visits only

URL: https://kabaido.ai/docs/changelog/2026-09-24-website-analytics-count-real-visits

Kabaido's own website figures now count only visits to the live site, so internal test runs no longer inflate them.

24 September 2026.

- Page views are recorded only on the live site. Internal test and recording runs are no longer counted.
- Nothing changes in your workspace.

## Service Centre inspection reads every option by its name

URL: https://kabaido.ai/docs/changelog/2026-09-24-inspection-reads-its-options

On the inspection form a declared choice shows as a person reads it, and a measured choice reprices the job exactly as the service defines it.

24 September 2026.

- The Declared column on Record inspection shows a choice by its name, such as OD only, instead of the code behind it.
- In a workspace whose families are not set up yet, a choice made in the Measured column now reaches the price exactly as the service defines it, so the recalculated price follows what the inspector recorded.

## A clearer website: one picture per section, shorter pages

URL: https://kabaido.ai/docs/changelog/2026-09-24-a-clearer-website

kabaido.ai says what each product does faster: every page opens with one picture of the product working, pages are shorter, and the detail waits behind a click instead of in the way.

24 September 2026.

- Every page opens with one visual: the product shown working, or on a trade page a photograph of the trade. Nothing overlaps, and the headline and the first action sit in the first screen.
- Pages are shorter and quieter: the homepage is about a third shorter on a computer and more than half on a phone, and the product and trade pages are about a third shorter.
- Reference detail (the full integration list, presets, related pages) folds into a disclosure you open when you want it.
- On a phone, Start free sits in the header, the footer folds its long lists and the product demonstrations rest on their result instead of replaying.
- In the platform, buttons that used the accent colour with white text now use the primary button colours, so they read clearly in dark mode, and fit labels read in plain sentence case.

## The repo cleaned, and the platform on a patched Next.js

URL: https://kabaido.ai/docs/changelog/2026-09-24-repo-cleaned

The platform runs on patched versions of its framework and of the libraries that read your files, and the documents we share by link are served from private storage. Nothing you use has changed.

24 September 2026. A background release.

- Security: the web framework and the libraries that read the files you send in (PDF, spreadsheet, Word and email) are updated to versions with no known advisories at the time of release.
- Documents we share by link are served from private storage through short lived links. Every link already sent still works.
- Faster checks behind every release, so fixes reach you sooner.

## Kabaido 1.0 Anthracite

URL: https://kabaido.ai/docs/changelog/2026-09-23-anthracite

Kabaido relaunches as the AI-native industrial operations platform built around the engineering of your industry: every product live on kabaido.ai, a new website and documentation, and a platform that shapes itself to the products you switch on.

23 September 2026. The first release of class 1, Anthracite. Industrial operations, transformed: the engineering behind everything you sell, built into the platform you sell from.

### What 1.0 is

- Products you switch on by need, never by plan: Sales Engineer and Design Engineer for sales, Route, Source and Stock for logistics, Service Centre and Machinist for production, Wizard, Inspect and Commerce for marketing.
- One workspace that adapts: the menu, the areas, the views, what the AI can do, the tours and the setup checklist all follow the products you have.
- One AI input for the whole workspace, powered by Application Engineering Intelligence, that cites what it reads and asks rather than guesses.
- Every plan carries every product; plans differ by usage and scale only, and there is no overage.

### New since the last release

- The menu is quieter: every area has its own outline icon, a short menu reads as one list, a longer one is grouped and each group folds away.
- Your AI chats are back in the menu under Recents, on every screen, with All chats to search every one, archived included.
- The new website is live on kabaido.ai, with a page for each product, area, part, trade and integration, and the documentation rebuilt product by product.
- Every old address, including the old language addresses, sends you to its page in one step.
- The Inspect map is public and live, with the counties mapped so far and a form to request yours.

### Retired

- The old positioning lines and the retired plan names and prices.
- The language versions of the website, which return one language at a time after 1.1.
- The announcement bar and the drawn app menu in the website's demonstrations.

## The documentation, rebuilt product by product with the real screens

URL: https://kabaido.ai/docs/changelog/2026-09-23-the-docs-rebuilt

The documentation now follows the platform: a guide for each product, area and part, procedures as numbered steps with the real screens in light and dark, and this changelog open with the version each release shipped in.

23 September 2026. The documentation for 1.0 Anthracite.

### The guides

- A landing for each product that opens with what it does, then where it lives, how to switch it on and off and every guide under it.
- A page for each area and each part, built from the same registries the platform runs on, so a guide cannot describe a view the platform lacks.
- Commerce covers the customer sign in on your Kabaido address, the same surface on your own domain and the website build.
- Inspect explains how a county is mapped, where the public figures come from and how to request yours.
- Every integration has its own page with the label the website shows: works today, template, via automation or roadmap.
- The API, webhooks, the MCP server and the rate limits have their own section, with the code samples run against the platform in tests.

### Easier to use

- A procedure is a set of numbered steps naming the screen and the button, with pictures of the real screens in light and dark.
- The docs follow your light, dark or system theme, and search reads every heading and every step.
- Every page that moved sends you to its new home in one step.
- The changelog lists every release with the version it shipped in.

## Every page of the new website, each drawn from the platform itself

URL: https://kabaido.ai/docs/changelog/2026-09-23-every-page

Every product, area, part, trade, design module, wizard, machine module, service model and integration now has its own short page, generated from the same registries the platform runs on, so the site can only describe what the platform does. The new site is on the preview, not yet live.

23 September 2026. The website track of 1.0 Anthracite, on its preview until the relaunch.

### The pages

- A page for each product, in the order its description is written: what it does, who buys it and uses it, who to involve, where it works, its modules, its integrations and the trades that use it.
- A page for each area of the platform and each part, and a page for each pairing that does something only that pairing does, such as Stock with Route or Pricing in Quotes.
- A page for each trade, built on the presets that serve it, and for each design module, wizard, machine module and service model a preset installs today.
- A page for every integration with an honest label: works today, template, via automation or roadmap.
- Inspect is now a live map of the counties mapped so far, with a form to request yours.
- New pages for pricing, security, AEI, how it works, why Kabaido, FAQ, about, contact, the blog and the legal documents.

### Shorter and clearer

- Less text on every page: one short line where there were paragraphs, and a picture of the real screen where there was a description of it.
- Photographs of real work on the product and trade pages.
- Every retired address sends you to its new page in one step.

## A new homepage, a new header and footer, and the platform drawn from itself

URL: https://kabaido.ai/docs/changelog/2026-09-23-the-new-homepage

The website's front door is rebuilt on the 1.0 design system: a new homepage that shows every product with its own real screen, a header with four menus and a site search, a new footer, and a reader that will say what Kabaido would do for any industrial company's website. The new site is on the preview, not yet live.

23 September 2026. The website track of 1.0 Anthracite, on its preview until the relaunch.

### The homepage

- Industrial operations, transformed. The engineering behind everything you sell, built into the platform you sell from. Start free, or book a walkthrough without leaving the page.
- Under the headline, a request typed into the AI, the quote lines it became and the catalogue match it made, drawn by the platform's own components rather than pictures of them.
- A strip of live figures from Application Engineering Intelligence, read from the same source as the public figures route. A number that is zero or missing is left out, never shown.
- Every product as a card with its official icon, its first sentence and its own screen, still until you point at it, then showing the one thing it does.
- A small live figure from Inspect: the regions mapped and the companies in them, linking to the map.
- Sections on how the platform adapts to the products you switch on (try the switches), how AEI reads a request, what your customers see, the integrations with an honest label on each, how your data is kept, three ways to start and the trades we know.

### Around every page

- A header with four menus: Products by element with their official icons, the Platform's areas and parts, Solutions by trade with the ready made design modules, wizards, machine modules and service models, and Resources. Pricing, a site search over the pages, the docs, the blog and the integrations, and Log in, Book a walkthrough and Start free.
- One booking dialog on every page, so Book a walkthrough never leaves the page you are reading.
- A new footer: every product, every trade, the platform's areas and parts, the company pages, the theme switch and the version.
- A short call to action at the foot of every page but pricing and contact, naming the product, area, part or trade you are reading about.
- The page uses the width of the screen rather than a narrow column, on one type scale, with one moving gradient per page at most.

### What Kabaido would do for your business

- Paste a company website into the homepage and Kabaido reads its public pages and says, in plain words, which products would help and what to try first, with a link to each. It answers only industrial businesses, never states a price and never invents a fact about the business it read.
- It runs on its own capped key with a daily spending limit and per visitor limits, and it stays switched off until the relaunch.

### Smaller

- Sharing a page now shows a card with its title and one illustration on the brand blue.
- The public Design Engineer previews are gone from the website: the configurators run in the platform, and the try it links go to sign up.
- Pages load one font file fewer: the italic face now loads only where italic text appears.

## Invite people by the job they do, and work at a station from your own menu

URL: https://kabaido.ai/docs/changelog/2026-09-23-roles-stations-and-guides

Invite someone by the job they do and they arrive with the right role, the right areas and the right stations. A station opens from your own menu and hands you straight back, the operator role never sees a price, and every area explains itself the first time you open it.

23 September 2026.

### People, and what each of them sees

- Invite by the job someone does. Pick a template such as Internal Sales, Applications Engineer, Stores, Operator or Finance and the invite carries the role, the areas in their menu and the stations they work at. Only the templates your workspace can use are offered. Customise any of it before you send, and save what you made as a template of your own for the next person.
- Access, beside each person in Settings then Users, changes their areas and their stations at any time. An area left out of someone's menu is closed to them, not just hidden.
- The operator role sees the work and never a price: no quote values, no order totals, no rates and no margins on any screen they can open.

### Stations, from your own menu

- The benches, machines, vans and scan points you hold are listed under Stations in your menu. Open one and it runs under your own sign in: everything you record there carries both the station and your name, and one click takes you back to the workspace.
- A screen signed in with a device key opens its own station and nothing else in the workspace.

### Presets that know what they need

- Each preset says which products it needs. Turning on one that needs a product you have not switched on asks first, and you can install it without that product instead.
- Presets can now set up machines. The plate profiling and PCD tooling presets add their machines as stations, waiting for you to issue each one a device key.

### Setting up

- A new workspace is set up in four short steps: your name, your organisation and what it does, the products you need, then the presets. What your business does ticks the products most like it, and only the presets your products can carry are offered.
- The Support page sets out three ways to get set up: yourself, with us online, or in person for a larger setup.
- Where one missing piece would help, such as a logo on your quotes or accounting behind your invoices, a short note sits where it matters, and each note appears in one place only.

### Guides

- Your first visit starts with a short tour of the AI, then one of your menu, built from the products you have switched on. After that every area, view and settings section explains itself the first time you open it, and a guide you skip stays skipped.
- On a phone the tour points at the menu and search buttons rather than at a menu that is closed.

### Smaller

- Customers has a Contacts view: every person at every customer in one searchable list.
- A wizard now shows where it runs: for your team, for your signed in customers once Commerce is on, and on your own website through the embed.
- The menu is narrower and sits closer to the top left, with tighter rows.
- A screen signed in with a device key landed on the member sign in page instead of its station. It opens its station now.
- A guide skipped the moment it opened could come back on your next visit and stop the next area's guide from opening. It stays skipped now.
- Someone with the operator role was offered links into Machinist setup that they could not open. The shop view no longer offers them, and setup says plainly who looks after it.

## One place to ask, and it knows your workspace

URL: https://kabaido.ai/docs/changelog/2026-09-22-one-ai-interface

The AI area is now the only place to ask anything. What it offers follows the products your workspace has switched on. It knows how your workspace is set up and what you have corrected before, and knowing it draws nothing extra from your usage.

22 September 2026.

### One place to ask

- The help chat, the design assistant, the Inspect agenda, price list and debrief boxes, the offering drafter and the schema reader have all moved into the AI area. Where one of them used to sit, a quiet link now opens the AI area with the question already written and waiting for you to send.
- What this can do here, beside the box, lists what your workspace can ask for: service history and what is due, jobs and the schedule, deliveries and today's runs, stock on hand and adjustments, supplier requests and purchase orders, enquiry replies and your website's week. Switch a product off in Settings then Products and its part of the list goes on the next load; ask for something your workspace does not have and it says which product would do it.
- A write is never done for you. When an answer can raise a job, record a stock adjustment, draft a supplier request or send an enquiry reply, it sets out every field first and does it only when you press confirm.

### It knows your workspace, and your customer

- Every answer is written knowing what your workspace does: your trade and your products, your service models and design modules, the fields you keep on a customer. A coater is answered as a coater.
- Pin a customer on the chip beside the box and the answer knows them too: how often they order, what they usually buy and in what quantities, what is open and what is overdue. When a request names a customer you have, the chip offers them; nothing about a customer is used until you pin them, and nothing about any other customer ever is.
- When you correct it three times the same way, it remembers: a product you keep choosing for the same wording is chosen for you, with a note saying why, and an answer you keep giving becomes an assumption it states and you can change. Settings then Organisation lists what it has learned, and Forget removes any of it.
- None of this draws on your usage. The context it carries is paid for by sending less of what it did not need.

### Your threads

- Threads now sit on the left of the AI area: pinned first, then today, yesterday, the last week and the last month, thirty at a time as you scroll. Search finds a thread by its title or by what was asked in it, archived ones included, and each can be renamed, pinned, archived or restored.

### Your customers' assistant

- The assistant on your customer sign in now runs on the same foundations. It is off until you switch it on and reads only the signed in customer's own quotes, orders, items, deliveries and documents. An attempt to steer it, in any of ten languages, is refused before it reads anything.

### Smaller

- Asking about a serviced item's history, or what is due, answered not found even when the item existed. Both answer now.
- A services workspace with many parameters per service had some of them left out of what the AI was told, so a request asking for masked threads or a PPAP pack could not be priced with them. Every parameter is now included.
- Someone with the operator role sees answers without prices, as they do everywhere else.
- The usage card beside the box closed again a moment after it opened, whether you hovered or tabbed to it. It stays open now.
- On your customer sign in in dark mode, a customer's own message was pale text on a pale bubble. It reads clearly in both themes.

## Take one thing out of a pack, and see the tool you are measuring

URL: https://kabaido.ai/docs/changelog/2026-09-22-one-item-on-its-own

The presets area lists the library two ways now: the trades, and every individual schema, service, design module and wizard inside them, each switchable on its own. And a dimension label on a 3D model no longer sits on the part it is measuring.

22 September 2026.

### One item, without the pack around it

- A preset is a pack: a trade's schemas, services, modules and wizards together. That is the right unit for the question "what do you sell" and the wrong unit for every question after it. Until now the only way to get one thing out of a pack was to install the pack and archive the rest, which left a workspace saying it was in a trade it is not in.
- The area now carries two filters ahead of everything else. Packs is the screen as it was. Everything in them lists each individual thing the packs carry, one row apiece, filtered by Design Engineer, Machinist, Wizard, Catalogue, Services or customer fields.
- Every row says what it is, which packs carry it and whether it is on in this workspace, and can be turned on or off on its own. A service model is deliberately not in that list: a route, a rule set and a set of standard times only mean anything beside the service they price, so it stays a pack decision.
- Turning a pack off never takes away something you turned on by hand, and turning one item off keeps anything an installed pack still asks for. Nothing is deleted either way: a schema with products in it is kept, a service is paused with its history, a customer field is archived with its values still on the records.
- One function creates the rows for both, so a schema turned on by itself is the same row, stamped and reported the same way, as the same schema arriving inside a trade.

### The dimensions on a model

- A dimension label was drawn at the midpoint of its own leader line, which on a thin part is the one place guaranteed to be ON the part. On a carbide endmill that put four labels across the flutes, the tip and the shank of the thing the reader came to look at.
- Labels now stand off the geometry, pushed out from the middle of the model with a hairline leader back to the dimension they belong to, and they are drawn smaller: annotation on a picture rather than body copy laid over it.
- A Hide dimensions button sits at the top left of the viewport. With them off the part reframes to fill the panel, which is what you want when you are showing somebody the tool rather than reading it.

## A dimension label is the same size on a 12 mm endmill and a three metre balustrade

URL: https://kabaido.ai/docs/changelog/2026-09-21-callout-labels-and-a-wider-rail

The labels on a design module's 3D view were sized by the inverse of the part, so a small tool drew them at twice their type size and a long run would have drawn them under a pixel. They now read the same on both.

21 September 2026. Found by opening the solid carbide endmill module and looking at it, which is how the last three defects in this module were found as well.

### The labels on the model

- Every dimension label on a design module's 3D view carried a fixed scaling factor, and the scaling a factor gives is divided by how far away the camera is. The camera is parked to fit the part, so a small part put the camera close and blew the labels up, and a large part pushed it back and shrank them away.
- On a 12 mm endmill that drew four labels at twice their type size, piled on each other and on the tool. On a three metre balustrade the same labels would have drawn at well under a pixel.
- The factor is now derived from the same radius the camera is fitted to, so a label reads at its authored size on any part and still grows and shrinks as you orbit in and out, which is what a label attached to geometry should do.

### Smaller

- The machining tool selector's own copy carried four sentences with a comma before and, against the house rule. Corrected in the engine and in the seed, and pushed to the live preset.
- A wizard module can now be offered to a workspace without a preset install creating anything, through scripts/trial/enable-preset.ts, which refuses rather than recording an install it did not make.

## The insert on the screen is the insert on the sheet

URL: https://kabaido.ai/docs/changelog/2026-09-21-machining-selector-walked

Two corrections to the machining selector on the day it shipped: the turning scene draws the insert the specification actually recommends, and a cut described bigger than the stock it was described against is now said out loud.

21 September 2026. Both of these were found by sitting down and using the selector on a real workspace, not by running its tests. The tests were green over the first one.

### The picture said one thing and the sheet said another

- A milling answer names a tool, a turning answer names an insert, and the scene only ever looked for the tool. On a lathe it found neither and quietly fell back to its own stand-in: an eighty degree insert on a wide pocket, beside a specification recommending a fifty five degree one at half the size.
- Nothing looked broken, which is what made it worth fixing first. A reader believes a picture, and a picture that contradicts the sheet beside it is worse than no picture.
- The answer is now read back into the scene in one place, and the line under the tool is a row off the specification word for word. A test walks every operation the selector has and fails if any answer names a tool the scene cannot find.

### A cut bigger than the part is now said out loud

- A forty five millimetre slot in stock you said was forty millimetres thick used to be answered as though both figures were true. So did a hole out of the back of a blind part, a finished diameter bigger than the bar it is turned from, a bore that leaves no wall and a pass longer than the bar it runs along.
- Both figures are yours, so the answer names the pair that disagree rather than choosing between them, and it stays a full answer: the tables do not stop working because two numbers contradict each other.
- It is checked only against a size you actually gave. Skip the part step and the stand-in on the screen is a drawing aid, never evidence. A hole drilled through is exempt, because coming out of the far side is the point of it.

### Smaller

- The note under the part step said a block was assumed whatever stock form you had picked, in front of a bar.

## Tell it the job, it tells you the tool and the numbers

URL: https://kabaido.ai/docs/changelog/2026-09-21-machining-tool-selector

A machining selector in Wizard: describe the part, the material and the cut, and it returns the tool to use and the speed, the feed and the depth to run it at, every figure carrying the published table it was read from and matched against what you hold.

21 September 2026. Somebody rings a tooling supplier with a job rather than a part number. A sixteen millimetre slot in alloy steel, forty five millimetres deep, on a machining centre. The answer is a tool, a grade, a coating and four numbers, and it takes an applications engineer who knows which table to open and what the tables do not cover. That conversation is now a form anybody can fill in.

### The part is on the screen while you answer

- It starts as the stock you are cutting from: a block, a plate, a round bar, a tube or a casting, drawn to the sizes you type, and it changes as you type them.
- Choose the material and the part takes that surface. The same surfaces the design modules use, so a bar of stainless looks like the bar of stainless it looked like there.
- Choose the machine and the part turns to face it. A lathe lays the bar along the spindle and brings the jaws in, a mill sets the block on the table, a drilling machine stands the work under the spindle.
- Then the tool arrives, cutting where it will actually cut. The endmill sections are the measured ones from the design module, the insert sits in its holder at its lead angle, the drill has its point angle on it, and the path drawn through the part is the cut you described rather than a decoration: the slot at its depth, the pocket at its stepover, the roughing passes down the bar, the hole to its depth with its peck.
- When the form is done the part is shown machined, with the metal that came off taken off it.

### Every number is read from a table, and the table is named

- Sixteen work materials carry their ISO 513 application group, their machinability band and their Kienzle constants, and the cutting data comes from the published manufacturer tables for that band rather than from a curve fitted to them.
- Milling reads a carbide table or an HSS table by the substrate you chose, and the feed is clamped to the diameter span the table actually publishes instead of being extrapolated past its last row. Turning reads its own table by operation and band. Drilling reads its published speeds and its published feed per diameter.
- Where the physics is standard it is applied and cited: the specific cutting force from Kienzle for the cutting force and the power at the cut, the radial chip thinning factor when the stepover is under half the diameter, the effective diameter at depth on a ball nose, Taylor for what a speed change does to tool life.
- The finish you ask for is met from a published surface finish chart, forty eight cells of it, read the other way round to give the feed that reaches it. A finish no published cell covers is stated as not covered.
- Insert designations are decoded to ISO 1832 and the inscribed circle comes from the published size table for that shape rather than arithmetic on the size code, which is off by nearly a millimetre on a common size.
- Coatings are chosen from the publisher's own workpiece list, including what a coating is published as unsuitable for. Aluminium never gets an aluminium oxide coating here because no publisher recommends one.

### It answers with what you hold

- The specification is matched against your catalogue across the cutting tool, round tool and indexable schemas at once, and the match is scored on the things that decide the job: diameter, flute count, corner radius and coating on a solid tool, shape, size, grade and chipbreaker on an insert, and the ISO group the maker published it for.
- A holder is matched to the insert rather than scored as though it were one, and it is listed under the insert it takes.
- There is always an answer. When nothing you hold fits, the specification hands straight into the endmill design module to be ground to order, with the diameter, the flute count, the corner radius, the length of cut and the coating already filled in.
- When your range holds nothing of that kind at all, it says so plainly and names the kind it wanted rather than offering the nearest thing of the wrong sort.

### What it will not do

- It will not invent a figure. A material outside the published bands, a finish off the chart, an interrupted cut in a group nobody publishes a penalty for: each is stated as missing with the question that would resolve it, not filled with a plausible number.
- It has no machine in it unless you put one there. Tell it the spindle power, the torque and the maximum speed and the cut is checked against them and cut back if it has to be, with the reason on the screen. Leave them out and the cut is quoted and the check is skipped.
- It is a starting recommendation. Every figure is tuned at the machine, and the sources note on the results says the date the tables were read.
- Grinding, broaching and gear cutting are not in it. Turning, milling, drilling, boring, reaming, grooving, parting, threading and the tapping drill are.

## Endmills, ground to a drawing

URL: https://kabaido.ai/docs/changelog/2026-09-21-endmills-ground-to-a-drawing

Design Engineer makes solid carbide endmills and form cutters: the flute section, the end teeth, the coating and the blank, with the rod matched out of your own stock and a price as you type.

21 September 2026. A special endmill enquiry is a drawing and a conversation. A diameter and a flute count are the easy part, and behind them sit the flute section, the helix, the core, the gash and the relief on every end tooth, the coating, the grade and which rod in the rack it can actually be ground from. Most shops work that out by hand, one tool at a time.

### The tool on the screen is the real tool

- The flute sections are measured, not drawn. Forty six ground solid carbide tools were analysed face by face; the eighteen helically fluted ones gave one canonical section per flute count. A flute count nobody measured uses the blend of them, scaled to the core and the land you ask for.
- The run out is a wheel position, not a fade. It is the full depth flute section revolved about the axis the grinding wheel sat on when it left the work, and both measured wheel positions are offered. A flute too wide for the wheel to swing out of is ground out on a straight retract instead, and the cutting list says so.
- The end teeth are exact planes: the gash face through the cutting edge and the tip centre, the pocket ahead of each tooth, the flat land and the relief behind each end edge. Every one of them is a setting here because every one of them is a wheel setting on the grinder.
- Square, corner radius, ball and chamfer ends, one to fourteen flutes, any helix to sixty five degrees, a margin and a primary relief, a necked reach, a Weldon flat or a whistle notch, and through coolant holes that follow the flutes.

### The coating shows

- Pick a coating and the model shows it: over the flutes and however far past them you set, in the colour the trade names for it, with the shank left bright.
- That is not decoration. A coating puts four to ten micrometres on a diameter against an h6 shank band of eight to thirteen, and a shrink fit holder has no clamping range to absorb it, which is why a shank is normally left bare.
- Colour is an appearance and never an identification. A coating is known from what was ordered and what the coater ran.

### The blank comes out of your own rack

- The rod is matched on the largest ground diameter anywhere on the tool, not on the cutting diameter, so a necked or stepped special buys a blank that can actually make it.
- Ground h6 and as sintered are two products and the quote knows it: an as sintered blank carries its grinding allowance. The length is the finished length plus the one millimetre facing allowance a cut to length blank carries, plus whatever you set for the cut off.
- Grades are named by grain and binder, the way a rod line is specified, and are never cross referenced between producers. If nothing in your stock covers the job it says so rather than quietly pricing a blank you do not hold.
- The grinding is priced pass by pass and scales with the length of cut and the helix, because the wheel path is the length of cut over the cosine of the helix angle and fluting is the longest operation on the tool.

### A profile you upload becomes a form cutter

- Upload a DXF or draw the axial section of a form and it is scaled uniformly onto the cutting diameter, so an angle drawn at forty five degrees stays at forty five degrees. An inch drawing is converted and says it was.
- The flutes then follow the form: every station is the same section scaled to the radius the tool has there, so the flute keeps its share of the local section instead of cutting through the core where the form narrows.
- The tightest internal radius in the form is measured and flagged, because a concave radius can only be ground by a wheel edge smaller than it.

### What it will not tell you

- No cutting data. A speed, a feed, a chip load, a depth of cut and a tool life depend on the machine, the material and the setup, and none of them is derivable from the geometry.
- Drills, reamers and countersinks share the parameter set and are not built yet.
- Every rate it ships with is a modelled illustrative default. Set them against your own cell in Rates and stock before a quote leaves the building.

## The service matcher, and the special

URL: https://kabaido.ai/docs/changelog/2026-09-21-the-service-matcher-and-the-special

A servicing line matches your service definitions again; a special to a drawing that states nothing the range could identify it by is no longer answered with a choice of stock; and a fourth presentation joins the deck engine.

21 September 2026. A regrind batch read perfectly on a new workspace, twelve millimetres, four flutes, strip and recoat, and then priced nothing. That is the first of two corrections in this release, and it had been true in every workspace for a day.

### Service lines match again

- The release of 20 September removed a column from the services table that the AI interface's service listing still asked for. The database refused the request, the refusal was recorded and swallowed as an empty list, and every servicing line since was told that no service in the organisation matched it. The listing now names exactly the columns that exist, and the build fails if one of them ever goes.
- Nothing you had set up was lost. A request sent in that window can be sent again and prices from your definitions as before.

### A special is not a choice of stock

- A line that asks for a part made to a drawing, stating only its material, used to be searched against the range like any other line. Every stock item of that material fit it equally, and the reader was asked to pick the closest one for a tool that exists only on a drawing nobody had sent.
- The range is still searched first, so a special you actually stock under its own description is still matched. What no longer happens is the offer: when the search cannot separate the top candidates and the line states no dimension, number or designation, the line goes to the Design Engineer where a module fits it, otherwise to the made to specification card with the drawing asked for and the price left to you.

### A fourth presentation

- The deck engine carries a new presentation prepared for a cutting tool group in County Durham, in their own colours, with the surfaces that are theirs shown as theirs and nothing of Kabaido's commercial terms in it.

## Watchers, and the record

URL: https://kabaido.ai/docs/changelog/2026-09-20-watchers-and-the-record

Set a watcher on any area and it acts when something changes; every action anyone takes is recorded under one taxonomy; and there is now one place that says what Kabaido tells your team and what your organisation tells its customers.

20 September 2026. Things that matter happen while nobody is looking. A line falls under its reorder point on a Friday afternoon, a quote goes unanswered for a fortnight, a customer who used to order every month quietly stops, a delivery misses the window you promised. Until today Kabaido could switch on exactly four things and nothing else, and the only record of what anybody did was a list of pages they had opened. This release is about both.

### Monitors

- A monitor is a watcher you save against an area: a condition, a schedule and what to do when it becomes true. There is a Monitors button in the toolbar of every area that has kinds worth watching, and a summary of all of them in Settings then Notifications.
- Thirteen kinds: stock below a level, a reorder point reached, a customer gone quiet, a customer come back, a quote unanswered, a quote expiring, an order overdue, a delivery late, a service due, a machine idle, a supplier price moved, a signal on a company you are tracking, and any saved list crossing a number you set.
- Watching costs nothing. Every check is a plain query over your own rows, never a model call, and a test fails the build if an evaluator ever reaches for one.
- A monitor cannot tell you the same thing twice. Each kind decides what counts as the same event, and the database refuses the second one rather than the code remembering to.
- Every monitor has a daily limit. When it is reached it stops, records what it would have done and tells you once. A watcher can never mail a customer forty times.
- What it can do: raise a notification, send your customer one of your own templates, draft a purchase order in Source, chase a quote, add a company to an Inspect list, or call your own webhook.

### Integrations, honestly

- The catalogue now carries every system this market actually runs, grouped by the product it belongs to, and every entry carries one of four labels: works today, template, via automation, or roadmap.
- Works today means Kabaido code talks to that provider, and the entry names the file that does it. A test reads the disk and fails the build if one of them is a claim with nothing behind it.
- A template is a prepared recipe on one of the open paths with that provider's fields filled in, and it says what you still have to do. A roadmap entry says it is not built and offers a meeting.
- No integration and no API is gated by your plan any more. Plans gate usage and scale. Every plan can connect anything.
- New: your own calendar, so a delivery window or a site visit lands in the diary of the person who has to keep it. An accounting path that raises a draft invoice from an accepted quote or a confirmed order and reads the reference and the paid state back. The wizard embed key and the Commerce site connection, which existed and were nowhere to be found.
- The contact finders are ordinary connections now, in the same list as everything else, with their credentials in a store no member of your workspace can read.

### Everything is recorded

- One event name for everything anyone does, in every area, written by one function at the moment it happens.
- No gaps, and that is a fact rather than a promise: a test walks every action in the platform and fails the build on one that records nothing. Anything genuinely exempt is listed with a reason, and the list is capped by a number a reviewer watches move.
- The activity page's team view is no longer pages only: a control chooses pages, actions or everything.
- With Commerce on there is a Customers view, which is the first time you can see what your own customers did on your customer area.

### Notifications, both ways

- Settings then Notifications: every kind Kabaido raises to your team, with in app on or off, email straight away or in the daily digest, and an override for any one person.
- Every message your organisation sends its own customers, with its subject and its body editable, a palette of the fields you can drop in, and a preview against a real record of yours rather than a made up one.
- A notification stores what happened and its details rather than a sentence written at the time, so editing a template changes what people read, including on messages already raised.
- With Commerce on, a customer message carries your customer facing brand and links into your customer area. Without it, the same message still goes out under your own logo and colour with the links that already work. Nothing is hidden and nothing is refused.

## Route, and the floor

URL: https://kabaido.ai/docs/changelog/2026-09-20-route-and-the-floor

Route gets the confirmed order to the customer's door, by courier or in your own van, with proof at the door and the real cost of getting there; and Machinist runs the floor above the machine screens, with one job, one clock and one cost.

20 September 2026. The sixth release of the 1.0 programme covers the half of an order that happens after it is confirmed, and the half of a job that happens on the floor. An order that is confirmed is not an order that has arrived: between the two sit picking, packing, a label or a van, a window you promised, a signature at a door and a cost nobody was booking against the job. Route is all of that. Machinist already gave the operator a screen at the machine; now there is one job behind every nest and every run, and the minutes come from the scans rather than from a form filled in afterwards.

### The order reaches the door

- A delivery is one consignment: the address, the window you promised, the packages, the tracking and the proof. An order can have several, and several deliveries to one site on one van are grouped by the stop.
- The order now carries the address it is delivered to, frozen onto the delivery. A later edit to the customer's address never rewrites a note that has already been printed.
- A second axis beside the commercial status, from pending through to delivered, worked out by one function in the same breath as every delivery write, so the two can never disagree. No screen types over it.
- Proof of delivery is a signature, photographs, the printed name, the time and the place, recorded as a scan event on the delivery's own code. It is a trail, not a status flag. A failed delivery keeps its reason and can be rebooked as a new one: a failed delivery is never edited into a success.
- Delivery notes, packing lists, collection notes and the load manifest are real documents, branded like the rest.

### Couriers, honestly

- A generic labels and tracking connector for your own carrier account or aggregator is on the roadmap with no date: nothing a customer can reach switches it on yet.
- Every named carrier works today as a record you keep by hand, with its own label printed and its tracking address pasted once.
- Kabaido ships no tracking address prefilled, for any carrier, because an invented tracking link is an invented fact. A test fails the build if one ever appears.
- First party carrier connections are on the roadmap with no date, and the product, the integrations list and the docs all say the same thing.

### Your own vans

- Territories, vehicles, runs and stops. A customer with a Tuesday keeps their Tuesday: the planner opens the territory's next matching day and their stop is already on it.
- Road order sequencing with a map, a drag that always wins, and a distance labelled as planned and straight line every time it appears. Actual kilometres come from the odometer when the run closes.
- A stop with no pin sorts last and asks to be pinned. It is never guessed.
- Loading is built for a scanner: packages in reverse stop order, a missing count that stays red until it is zero, and a departure that asks why if the van leaves short. A parcel that is not yours joins the manifest with a label, so the manifest is complete even when the goods are not.
- Closing a run asks for the odometer, works out what the run cost from your own rates and shares it across the deliveries on it. A cost worked out from a planned distance is shown as planned, never as actual.

### The driver's screen

- Today's run, the next stop as one large card, and three things to do at the door: delivered, collected or failed. Navigate hands the stop to Google Maps or Waze.
- It works with the network off. Every action is saved on the device and sends itself when the signal comes back, in order, exactly once. Photographs queue too, and the screen says when there are too many to hold.
- A scan made in a blackspot is recorded at the time it happened, on the trail and in the stock ledger alike, so a day out of signal does not move the goods to the moment the van found a bar.

### With Kabaido Stock on

- A van is a location, a load is a transfer onto it, and closing the run reconciles it to zero.
- Without Kabaido Stock nothing is lost: the same issue and the same return are written at your one default location and every figure stays true. What Stock adds is the place to see them together.

### The floor, above the machines

- One job behind every nest and every run, carrying its own code through every station. Nothing on the machine screens moved: a machinist who used Arcline yesterday uses it the same way today.
- Machines are stations, each with its own screen at the machine, its own hourly rate and its own device key. That screen can move its jobs and reach nothing else.
- Operators, with what each is certified to run and what an hour of their time costs.
- A day and week board per machine, sized by standard minutes, with a late marker. The same jobs give the same board, and a drag writes the order and nothing else. No solver and no AI decide what you make next.
- Costs per job, machine, operator and month, standard against actual. Actual minutes come from the scans, and a typed correction is stored with the reason for it. Where a rate is missing the screen says so rather than showing a zero.
- Your customer can see the status of their own production order, and nothing else.

### Built to order

- Five design modules are listed as built to order with the work each would need first: solid round tools, machine knives, superabrasive wheels, woodworking cutter heads, and coating racks and jigs. Ask for one from the same card.

## One ledger, and the supply side

URL: https://kabaido.ai/docs/changelog/2026-09-20-one-ledger-and-the-supply-side

Stock keeps one ledger behind every quantity on the platform, and Source runs your suppliers, their prices, your requests, your purchase orders and goods in on top of it.

20 September 2026. The fifth release of the 1.0 programme gives every quantity on the platform one ledger and brings the supply side in. Stock is now a product of its own: one record of what is where, written by every receipt, issue, transfer, count and write off, and read by the catalogue, the design modules, the machine modules and the orders. Source runs your suppliers, their prices, your requests for quotation, your purchase orders and goods in, and every buy price lands in the same ledger with the cost it carried.

### One ledger

- Every balance is the sum of its movements. Nothing is typed over a figure any more: a receipt, an issue, a transfer, a count or a write off is a movement with who, where, when and why, and the balance follows.
- Locations are yours to name: a store, a rack, a bin, a van or a station. A station that holds stock has its own bin, and a scan at that station moves or counts into it.
- Stock has four views. Lines is every item at every location with what is on hand, reserved, free and on order. Locations is where things are. Movements is the ledger, newest first, filterable and exportable. Reorder is every line at or under its reorder point with the quantity to ask for, and from it you can request quotes or raise a purchase order in one step.
- A sales order reserves what it needs the moment it is confirmed and issues it when it is fulfilled. A sale that would take a balance below zero is refused unless you have said that line may go negative, and then it tells you.
- A count sheet records what was found against what the ledger said, and closing it posts the differences as movements with the variance on record.
- The quantities you already had, on catalogue products, design materials, machine shop material and plasma sheet stock, were carried into the ledger as opening balances with their cost. Every screen that showed them shows the same figure from the ledger now.
- Unit cost is a moving average recomputed on every receipt, shown to engineers and above and never on a customer document.

### Source

- Suppliers has four views: the supplier network with its approval state and performance, price lists, requests and a shortage list. A customer who also supplies you becomes a supplier in one step.
- A price list arrives as a CSV or is typed in, with breaks, validity and currency. Activating it shows what moved against the list before it, and a move past the alert you set raises a notification. A supplier price can be accepted as a product's cost basis in one action.
- A request for quotation goes to as many suppliers as you choose, each with their own answer link where they see only their own lines and prices and answer in the browser, or you type the answer from the quotation they sent. The comparison lays every answer side by side on quoted price, landed cost and lead time, and awarding it raises one draft purchase order per winning supplier.
- Purchase orders live in Orders under the Purchase view, with a PDF, an email to the supplier's contact, acknowledgement, expected dates and a state that follows the goods rather than a status somebody sets.
- Goods in posts against the order from the order itself or from the scan screen at the dock: what arrived, what was rejected and the lot code it now carries, and the ledger, the order and the on order figure move in one step. Over receipt beyond the tolerance you set is refused before anything is written.
- A supplier invoice is matched to the order and the receipts, and a variance outside your tolerance is flagged for someone to acknowledge.
- Exchange rates are yours to accept: nothing converts a cost at a rate you have not entered, and a landed cost that lacks a rate, freight or duty says what is missing rather than guessing.
- The API carries suppliers, purchase orders and stock, and the AI interface can read a balance or a shortage list when it is asked.

### What your customer sees

- Nothing of this. Suppliers, prices, purchase orders and stock levels never appear on the customer surface or on any customer document.

## One code for life

URL: https://kabaido.ai/docs/changelog/2026-09-20-one-code-for-life

Service Centre runs the work you do on a customer's own property from arrival to return, and every item, batch and package carries one scannable code with an unbroken record behind it.

20 September 2026. The fourth release of the 1.0 programme makes Service Centre a product of its own and gives the whole platform one traceability code. An item arrives, is identified, is measured, is worked on at several benches, is priced on what was found rather than what was declared, is packed and goes back, and every one of those moves is recorded, because the customer paid for a promise about their own property.

### One code, and the record behind it

- Every item, batch, package, job, delivery and stock lot takes one code that is scannable two ways: a QR a phone reads and a Code 128 line a wedge scanner reads, both landing in the same place. Every serial you have already printed keeps working for life.
- A code holds any number of outside references, so a scan of the customer's own asset number, a brand's factory code or a courier's tracking number finds your item.
- The record behind a code is added to and never edited: who touched it, where, on what and when, with the minutes between each move read from the scans rather than estimated. A status can no longer move without its record, and a record cannot exist without the move.
- Scan a label with no sign in and see exactly what you choose to show: nothing at all, the item and where it is, or the dates it moved. Nothing else, ever.

### The workshop

- Servicing has five views. Work ranks what needs doing and shows the jobs in progress and the queue at every station in minutes. Registry is every item you hold. Services are your service models. Rules are every setting the workshop has, in one place. Costing is your rates, your standard minutes and six reports.
- A service model declares the kind of work it is, the families of item it applies to, the benches it runs through, the minutes each should take and the rules it quotes under. Ten are ready for common trades and any of them is yours to change.
- A family is a class of item with its own fields: what the tool is, entered once, and what is measured every service. The inspector's form asks for those, with the customer's own limits shown as bounds the field will not cross.
- Rules decide what is asked, surcharged, refused or defaulted before anyone types anything, and a rule that changed a line says so on the line, in words.

### The floor

- A bench, a machine, a dock or a van signs in with its own device key and reaches one screen. A station is not a person: it records the work and never sees a price.
- The scan screen works on a phone at the bench, on a tablet on a stand, with a camera or with any keyboard wedge scanner.
- It also works with no signal. Scans are kept on the device with the time they were actually taken, and when the signal comes back they arrive in the order they were taken, carrying that time and not the time they were sent.
- Print a label in either of two sizes, a docket, a batch sheet or a packing list.

### What the work costs

- Set your rates once, per workspace, per centre or per station, each with the dates it applied from. Set the minutes a step should take. Every scan is then priced from them.
- The minutes between two scans are what the work actually took, so standard against actual is a column on every step, service, family, centre, customer and month, with the margin against the price beside it.
- A cost with nothing behind it is never invented: the figure says what is missing instead.

### What your customer sees

- With Commerce on, a customer signs in and sees their own items, where each one is, what was done, what is due back and the answers they have given, and can ask for a collection in one tap.
- They never see your minutes, your operators or your costs.

## Your customers sign in

URL: https://kabaido.ai/docs/changelog/2026-09-20-your-customers-sign-in

Commerce gives each of your customers their own sign in to their quotes, orders, documents and wizards, on your address and in your brand.

20 September 2026. The third release of the 1.0 programme brings the customer facing surface, and Commerce brings it. A customer of yours signs in with an access code you hand them, on kabaido.ai or on your own Kabaido address, and sees their own records and nothing else. A customer is never a member of your workspace: what they can read is decided in the database, row by row, and proven by a test that enumerates every table.

### The customer sign in

- A customer record carries an Access tab: create the code, copy the invite link, send the invitation, rotate or revoke it, and see who has joined and when they were last seen. A storefront account registered by your Commerce site links to the same record with no second identity.
- The surface shows the customer their quotations with accept and decline, their orders and where each one is, their documents, their saved designs, the wizards you open to them, and their items with the approvals waiting on them where Service Centre is on. Deliveries arrive with Route.
- A wizard a customer runs becomes a quote request in your workspace, marked as coming from the surface and naming who asked. A quotation you send appears on their surface the moment it is sent, and an acceptance raises the order.
- The account page lists every supplier that has given the person a sign in, and lets them leave one.

### Your address and your brand

- Two front doors onto one surface: the path on kabaido.ai on every plan, and your own Kabaido address on a paid plan. A subdomain of your own domain can serve it too, with the record to add shown in Settings and the state checked for you.
- Their surface, their brand: your logo, icon, wordmark and colour, in both themes. On a light colour the text switches to dark and buttons take the deeper tone, so everything stays readable.
- View as a customer from Settings to see exactly what one of yours sees.

### The customer assistant

- Off by default. When you switch it on, a customer can ask about their own quotes, orders, items and documents, or a technical question, and the assistant only ever sees that customer's own records, never your costs, your margins or another customer.
- Every answer draws on your workspace's usage, and each customer has a daily allowance you set.

### In the platform

- Settings then Customer facing holds the address, the domain, the brand, the areas customers may use and the welcome. The Commerce area's Customers online view shows who is signed in across your customers.
- Switching Commerce off keeps every row and closes both addresses; switching it on brings them straight back.

## Plans set usage and scale

URL: https://kabaido.ai/docs/changelog/2026-09-20-plans-set-usage-and-scale

Plans set usage and scale only, usage is one pool shown in plain words, and a daily budget keeps a busy day inside the month.

20 September 2026. The second release of the 1.0 programme rebuilds what a plan is. Pro is £189 a month, Ultra £549 with three and a half times the usage, Max £1,299 with eight and a half times, and Enterprise by agreement; five per cent off annual. Every product is on every plan. A plan sets how much usage and how much scale a workspace has and nothing else.

### Usage

- Everything a workspace does that costs Kabaido something draws on one pool: AI answers, Inspect profiles and exports, wizard runs, design exports and your customers' own use of the customer surface. There are no credits and no price per unit anywhere.
- The usage bar sits beside the AI input. Hover, tap or focus it and the card says how much of the month is used in plain words, what has used it, and when it resets. It is a share, never a number.
- An owner can set a daily budget in Billing: a fifth, a tenth or a thirtieth of the month, or a custom amount, in the workspace's own time zone. When today's budget is used, AI answers pause until midnight and everything you do by hand carries on.
- Upgrading mid month tops the balance up to the new plan's allowance straight away, once per period.
- The free plan holds a fixed allowance for the life of the account. It is for seeing the platform work; it does not refresh.

### Billing

- Billing shows the plan, the period, the usage in words, the daily budget, and the scale rows (people, products, services, design modules, saved designs, exports, stations, storage, Inspect profiles and wizard runs) as used against included.
- Inspect draws on the same pool. On the free plan it is a preview: the map and the lists, with no company opened.
- The Enterprise card says what an agreement covers and books a conversation. There is no overage on any plan.

### Also today

- Integrations, the API keys and the connectors are no longer gated by plan: a product that is on brings its connections with it.
- The pricing page, the plan grid and the documentation carry the new ladder.

## Products are the entitlement

URL: https://kabaido.ai/docs/changelog/2026-09-19-products-are-the-entitlement

Every workspace switches on the products it needs, and the platform arranges itself around them.

19 September 2026. The first release of the 1.0 programme changes what a workspace is. Until now a plan decided what you could open. From today a workspace holds the products its business needs, switched on in Settings under Products, and every plan carries every product: plans set usage and scale only.

### What changed for your workspace

- Your products were set from what your workspace already does. A workspace with quotes has Sales Engineer on, one with registered service items has Service Centre on, one with a wizard has Wizard on, and so on. Nothing was switched on that you had not used, and nothing you had used was switched off.
- A workspace that has not used anything yet is asked what it needs the next time somebody signs in. New workspaces are asked during setup.
- The sidebar, the workbenches, the AI interface and the setup checklist all follow the products that are on. Switching a product off keeps every record readable with a banner and refuses new writes; nothing is hidden and nothing is deleted.

### Meetings

A meeting booked with Kabaido is a Google Meet link on a Google Calendar invitation, sent by Google. The booking popout on the website and in the platform offers three start times a working day across three weeks, with England and Wales bank holidays left out, and the confirmation email carries a link to move or cancel the meeting without signing in.

### Also today

- The website and the platform are English only for 1.0. The nine translated sites are archived and return one language at a time after 1.1, and customer documents keep the language your organisation has set.
- Every colour on the site and in the platform now resolves to one calibrated palette, checked on every build. Light, dark and system are the three themes.
- The favicon is the Kabaido mark, brand blue in a light browser and brand white in a dark one.
- The paid extra machine screen is gone. The number of stations a workspace can run is part of its plan.
- On the free plan Inspect is a preview: the map and the lists, with no company profiles opened.
- The version you are running is stated on the platform's Organisation settings page and on the Kabaido team's own overview.

## Inspect is live

URL: https://kabaido.ai/docs/changelog/inspect-is-live

The fifth module is public: industrial customer intelligence for field sales, included with every plan.

31 August 2026. Kabaido Inspect is out in the open. It has been built and running for entitled accounts since July; from today it is a module anybody can read about, ask for and switch on, and the platform is five modules rather than four.

### What it does

Inspect maps every manufacturer in a region into an engineering grade profile built from public evidence, then turns that into what a field representative needs before a first conversation: the three of your offerings that site's evidence actually supports, the questions worth asking, who to speak to and what happened last visit. Every profiled value carries its sources and whether it was verified or inferred, and a gap is listed as a gap rather than filled in.

### What it costs

Nothing on top of your plan. The plan sets how many company profiles you can open a month, browsing the map and the lists costs nothing at all, and documents, stored contacts and debriefs draw on your ordinary monthly usage. See [Billing for Inspect](/docs/inspect/billing).

### Where to start

[Inspect overview](/docs/inspect) explains the two layers and the first three things to do. [The offering map and the two documents](/docs/inspect/offering-and-documents) is the page worth reading before your first visit brief.

### Also today

- The Machinist section gained pages for the wire EDM and CNC milling modules, and the Wizard section for the PCD saw blade and coating selectors.
- Commerce gained a section of its own for the workbench that ships with a connected site.
- Support was simplified to one conversation with the ways to reach a person beside it, and every support conversation is now visible to the Kabaido team so a question the assistant could not answer becomes a documentation page rather than disappearing.
- The website was walked page by page against the platform as it now is. The Wizard page had been publishing twice the free plan's real monthly run allowance since the page was written; it now reads the figure from the plan itself.

## Commerce is a workbench

URL: https://kabaido.ai/docs/changelog/commerce-is-a-workbench

A connected Commerce site is now run from inside the platform, and notifications arrive as they happen.

30 August 2026. Until now the Commerce area described the offer and booked a meeting. It still does that when you have no site, but a connected Kabaido Commerce website now opens a full screen workbench of its own, the same way Wizard and Machinist do.

### What the workbench holds

- Overview: live activity from your site as it happens, with visitors, orders, enquiries and selector runs over the last two weeks.
- Content: every text and image slot on the site, with the photography that is in place and the shots still awaited tracked honestly.
- Enquiries: messages sent on your site, with reply and close built in. Replies go from your workspace and are logged like any other email.
- Blog: what is published and what is planned next.
- Checklists: the real launch and growth steps of your project, ticked off as they land.

### Nothing lives twice

Products on your site are your catalogue records. People who register on your site appear in Customers. Orders placed on your site are platform orders with the same numbering, documents and notifications as any other, and the order number your buyer saw travels with them. You can invite an existing customer to the site by email in one click.

### Priced by length

The catalogue gained a semi-custom product type for things sold to a dimension: a bandsaw blade welded to length, cord or belt by the metre. One dimension drives the price through a rate, with an optional fixed addition and a minimum charge, and quantity breaks layer on top exactly as for a fixed price. Quotes and orders ask for the dimension and price the line from it.

### Notifications now arrive

When something worth knowing happens, a small box appears top right and gets out of the way by itself. Important things stay until you dismiss or open them, and several stack in a list. Dismissing a toast never touches the notification: it stays in the bell exactly as it was.

## Credits are retired

URL: https://kabaido.ai/docs/changelog/credits-are-retired

You buy an amount of usage a month. No credit counts, no price per credit, no overage.

30 August 2026. Kabaido used to sell a complexity-weighted credit. A plan included a number of credits, the pricing page published a weight table and a price per extra credit, and to work out what a month would cost you had to learn a unit first. That is gone. A plan now includes an amount of AI usage a month, and nothing anywhere states a credit count or a price per credit again.

### The plans

Free, Pro at £149 a month, Ultra at £449 with five times the Pro usage, Max at £1,249 with ten times, and Enterprise by agreement. Annual billing keeps its 5 per cent discount. If you were on Starter you are now on Pro, Growth is now Ultra and the old Scale is now Max: the same price, the same limits and more usage than before.

### There is no overage

No plan meters a per-unit overage any more. When the month’s usage is spent, the AI pauses and everything else carries on: quoting, orders, the catalogue, the configurators, the wizards and the machine screens. The allowance resets on your billing date, and upgrading lifts the limit straight away. You cannot receive an invoice for usage you did not agree to.

### What the pricing page shows instead

Roughly how many multi-line quotes, resolved request lines, AI design runs and drafted email replies a month each plan comfortably handles. They are worked examples computed from the real allowance, labelled as examples, because the honest way to size a plan is to start small and watch what your own enquiries use.

### Commerce and Inspect

- A Kabaido Commerce website no longer carries a separate monthly hosting line. It is a project we quote and build, typically £6,500 to £12,500 depending on complexity and billed as two invoices, and it then runs on your ordinary Kabaido plan.
- The Inspect add-on is withdrawn. Inspect access comes with your plan, and the plan sets how many company profiles you can open a month.

The Billing page now shows one usage bar: how much of this month is spent, when it resets and roughly what the rest is worth in quotes. Extra machine screens are unchanged at £49 a month each.

## Activity, and one screen per module

URL: https://kabaido.ai/docs/changelog/activity-and-one-screen-per-module

Kabaido now tells you what happened, and Wizard and Machinist open on the work instead of on a menu.

28 August 2026. Kabaido has recorded what happens in a workspace since the day it launched and shown almost none of it to the people it was about. A customer opening a quote was written to the document trail and to nobody. A service item passing its due date was ranked by a dashboard you had to already have open. An automation sent an email on your behalf and left a timestamp on a settings row. That is fixed, and two module areas were rebuilt at the same time.

### Activity and notifications

There is a small bell at the top right of every screen in the platform. It opens the workspace's stream, ordered by what needs a decision first rather than by what happened last, so an overdue service item sits above a design somebody saved a minute ago. Unread rows carry their weight, read rows lose it, and opening a row marks that row read rather than the whole list.

- Quotes: sent, opened by the customer, accepted, declined, expiring, expired and chased. The one people wait for is opened, and it arrives once a day per quote however many times it is read.
- Orders raised, moved and varied. Requests arriving from a connected inbox or an integration, and replies the email agent has prepared for you to check.
- Service items falling due and going overdue. Imports finishing and failing. Automations that actually did something. Members invited, joined and moved. Plan changes, failed payments and a low credit balance.
- Machinist nests cut and sheet stock going low. Inspect unlocks and new signals. Presets turned on and off.

The full list lives at Activity in the main menu, with three lenses: Notifications, Setup, and Team, which shows admins and owners who has been where in the workspace.

### The setup checklist moved

It used to sit under the box you type into, which is the one place on the screen that should be empty. It is in the Activity panel now, it is longer, and it only asks for things your workspace can actually do: an organisation with no design module on is never told to save a design. Under the composer instead is a quiet row of links to the modules you have switched on and the work you had open.

### Wizard is one screen

Wizard used to be a gallery of cards you clicked through to reach the part that does the work, and the answer then arrived at the bottom of a long page, below the model, where people did not find it. Now Products, then Wizard opens straight on the selector: the form on the left, the live scene in the middle and the results on the right, on screen the whole time. Press See matches and the rail is already there.

The same rail carries the wizard's activity and its usage: how many runs, how many found something, where the runs came from and what people are asking for, all counted from your own runs and never modelled. The bandsaw scene now wears real photographed material surfaces, scaled to the real size of the section, so a 50 mm bar and a 200 mm box show the grain at the same scale.

### Machinist is one screen

Machinist used to be a page with two cards on it, and Arcline underneath it spread over seven entries in the sidebar. Clicking Machinist now opens the module itself, with five views along the top: Shop, Parts, Orders, Nest and cut, and Setup, which folds machines, sheet stock and the cut chart into one place. Quick actions and the counts that matter are on the toolbar wherever you are.

### Presets say what they bring

Every preset in the list now shows, at a glance, what it installs and how much of it: the design module, the machine interface, the wizards, the product schemas, the services and the customer fields, with its family in its own colour. You can filter by what a preset brings rather than reading thirty two names. Plate profiling now brings the Arcline machine interface with it, and there are three clearly named paths for a custom module, machine interface or wizard when nothing on the list fits.

## The Wizard website add-on is withdrawn

URL: https://kabaido.ai/docs/changelog/the-wizard-add-on-is-withdrawn

A wizard on your own website is part of a Kabaido Commerce website, not a separate monthly line.

28 August 2026. The £49 a month Wizard website integration add-on has been withdrawn. It was sold as something an organisation bought in Billing and then set up in Settings, which was never how it actually worked: a wizard cannot appear on a website unless somebody builds it into that website, and that somebody is Kabaido.

### What changes

- A wizard on your own website is now part of a Kabaido Commerce website and nothing else. There is no separate monthly line to buy and no key to create.
- The Wizard section under Settings, then Integrations, is gone, along with the Wizard panel in Billing. The Kabaido team connects your site during the website build.
- Sites that were already connected keep working exactly as they did. Nothing goes dark and no key was changed.
- Running wizards in the platform is unchanged: free on every plan, 20 runs a calendar month on the free plan, uncapped on paid plans, and never a credit.

### Where a website wizard comes from now

It comes with a Kabaido Commerce website: one-time setup POA, then £129 a month hosting and management, with the wizard built into your pages against your own catalogue. See [Commerce](/docs/commerce) and [the Wizard overview](/docs/wizard).

## Presets, and one Services page

URL: https://kabaido.ai/docs/changelog/presets-and-the-services-page

Turn on everything one trade needs in a single step, and see what needs doing in Services rather than where everything is.

27 August 2026. Setting Kabaido up used to be four separate decisions on four separate screens: which of twenty five product schemas, which of sixteen service definitions, which design modules and a wizard nobody had been told about. None of them is answerable on the day you sign up. There is one question now, and it is one you can answer: what do you sell, and what do you service.

### Presets

A preset is everything Kabaido needs to know about one thing you sell or service, turned on in one go: the design module, the product schemas, the service definitions, the wizards and the extra customer fields that trade works with. There are thirty two of them in six families, under Products, then Presets.

- Several can be on at once, and most businesses need several. Turning one on costs nothing and is not a plan gate.
- Service definitions arrive switched off, because their figures are illustrative starting points rather than your rates.
- Turning a preset off keeps everything you have filled in. Schemas with products in them stay, services are paused with their history rather than deleted and customer field values stay on the customer.
- The product schema library in Catalogue now offers what your presets carry rather than every schema in the supply chain. Until your first preset is on it still shows everything, and nothing you already use is ever hidden.
- Presets never change what the AI knows. Full Application Engineering Intelligence stays on for every organisation, all seven categories and all fifteen packs.
- Documented in [Presets overview](/docs/parts/presets).

### Onboarding asks what you sell

Onboarding has a fourth screen. It asks which product groups you sell, from a plain list, and switches on the presets that match what you pick. Nothing is invented for you: no sample products, no example customers and no made up prices. Documented on [Create your account](/docs/getting-started/create-your-account).

### Services is one page

The Services area was three tabs and a board, which told you where every item was and never once told you which one to pick up. It is one page now, led by what needs doing: every open item ranked, past its promised date first, then due within three days, then longest waiting, each row carrying the one action that moves it on. A status strip filters that list, the serialised item registry sits under it and the services you offer sit under that.

- A service definition can declare a turnaround in working days, and an item takes its promised date back from it at the moment it is booked in.
- Items can be registered straight from an order.
- Serials, QR dockets, the event timeline, the lifetime count and the inspection and approval flow are unchanged.
- Documented in [The work list and inspection](/docs/service-centre/the-inspection-queue) and [Building a service](/docs/service-centre/service-models-and-workflow-types).

### The Custom area opens on your work

Products, then Custom, no longer shows a page of cards with a switch on each. It resolves straight into the workbench: the file you had open, else the newest one in your workspace, else a fresh file on the module that suits your business. Design modules arrive with the preset that carries them. Documented on [the Design Engineer module page](/docs/design-engineer).

## Meeting transcripts

URL: https://kabaido.ai/docs/changelog/meeting-transcripts

Meetings held in Kabaido Meet write their own transcript, with everyone in the call told.

20 August 2026. A meeting you hold in Kabaido Meet now writes its own transcript: speaker by speaker, in the order things were actually said, searchable afterwards and attached to the company and the person it was with.

### What happens

- The audio is captured in the host's browser, one recording per person, which is why every line carries the right name without any guesswork.
- It is transcribed on Kabaido's own hardware by an open source speech model that runs offline. Nothing is sent to an AI provider, there is no summary and no analysis, and nothing is used to train a model.
- The audio is deleted as soon as the transcript is written, usually within minutes of the meeting ending.

### Telling people

Recording someone without telling them is not acceptable and in the UK it is not lawful, so the notice appears three times: in the invitation email, on the screen before anyone joins, and as a state that stays visible to every participant for the whole time it is running. The host can stop it at any moment, and stopping takes effect immediately.

- A meeting can be switched out of transcription entirely, before it starts or during it.
- Meetings held before 20 August were never recorded, so they have no transcript and never will.
- Documented on the Kabaido Meet page at the time; that page and the product were retired on 19 September 2026 in favour of Google Meet, see the booking a meeting page.

## Kabaido Meet and the Wizard

URL: https://kabaido.ai/docs/changelog/meet-and-the-wizard

Live meeting rooms in the browser, deterministic product selectors and extra machine screens.

August 2026. Two surfaces shipped in late July and are live for every account: Kabaido Meet and the Wizard. The machine screen add-on landed alongside them.

### Kabaido Meet

Kabaido now runs its own meeting rooms. Every meeting booked through Kabaido carries a kabaido.ai/meet link with a code, and guests join in the browser with no account and no download. Prejoin carries a camera preview, device pickers, background blur and noise cancellation; hosts can lock the room, mute or remove a participant and end the meeting for everyone. Meetings were not recorded at launch; transcripts arrived on 20 August and are covered in the entry below.

- Booking through Commerce, Support, Design, Machinist and the website contact page now issues a Kabaido Meet link, falling back to a Google Meet link if a room cannot be created.
- There is no AI in a Kabaido Meet call and it consumes no credits.
- Documented on the Kabaido Meet page at the time; that page and the product were retired on 19 September 2026 in favour of Google Meet, see the booking a meeting page.

### The Wizard

The Wizard is a platform area of deterministic product selectors: engineering forms that compute a specification from published engineering data and match your own catalogue against it, with no AI in the loop. The first preset is the bandsaw blade wizard, whose reference tables are published in full.

- Running wizards in the platform is free on every plan and never consumes credits; the free plan includes 20 runs a month and paid plans are uncapped.
- Website integration, showing a wizard on a commerce website built by Kabaido, was £49 a month per site and requested as part of the website build. That add-on was withdrawn on 28 August 2026: see [The Wizard website add-on is withdrawn](/docs/changelog/the-wizard-add-on-is-withdrawn).
- Documented in [the Wizard overview](/docs/wizard).

### Extra machine screens

Every plan includes one connected machine screen, the free plan included. Extra screens are £49 a month each on any paid plan, and caps enforce softly: a running machine screen is never disabled mid-job. See [the Machinist module page](/docs/machinist).

## The platform refit

URL: https://kabaido.ai/docs/changelog/the-platform-refit

Kabaido is now one platform with four modules: Sales Engineer, Design Engineer, Commerce and Machinist.

July 2026. The platform has been rebuilt around four modules on one account.

### New in this release

- The four modules: the Sales Engineer flagship, the Design Engineer for custom product sales, Commerce as a managed store and trade portal and the Machinist for screens at the machine.
- The unified platform navigation: New request, Search, Sales, Products, Machinist and Commerce, with Settings, Support, Docs and the theme switch in the profile popout.
- The email agent: connect a Gmail or Microsoft 365 inbox and the Sales Engineer reads, classifies and drafts replies to the enquiries that already arrive there, in review mode by default.
- The scheduling engine: book a meeting with the team from Commerce, from Support or from the website contact page.
- Arcline, the CNC plasma and sheet metal fabrication preset: parts and a CAD editor, sheet and remnant stock, cut orders and nesting with simulation and G-code and DXF export.
- Application Engineering Intelligence presented in full: seven categories and fifteen knowledge packs, selected per request, documented in [Application Engineering Intelligence](/docs/platform/application-engineering-intelligence).
- The new website, rebuilt around the four modules with a page per module and an AEI page.

The docs were restructured to match: the old Configure section is now Design Engineer, and new sections cover the four modules, the Machinist and the email agent. Old links redirect.

## Documentation expansion

URL: https://kabaido.ai/docs/changelog/documentation-expansion

The docs now carry live UI previews, a full security and compliance section and complete plan, role and integration references.

June 2026. The documentation has been expanded to capture the platform in full, with the same honesty rules as the product: every number quoted from the running code and every preview rendered by the real components.

### New in the docs

- Live UI previews embedded across the docs: the envelope, citations, catalogue browse, configurator runs, the service register and timeline, quote lines, the credit meter and the API console.
- Security grew from an overview into a full section: tenant isolation and access control, encryption and credentials, AI data handling, compliance and GDPR, platform and payment security, and export and deletion.
- Users, roles and permissions: the exact five role capability matrix and the owner safeguards.
- Matching documented to the numbers: fit bands, satisfaction scores, tolerances, equivalents and where the AI does and does not touch a match.
- Integrations gained customer connections, the graded provider directory, the webhook retry schedule and the full scope table.
- Billing now lists every plan limit, overage rate and the free plan caps in one place.

## Launch

URL: https://kabaido.ai/docs/changelog/launch

The first release of Kabaido: requests read with citations, catalogue import, configurators, servicing, quotes and a free plan.

Kabaido launches with what is now the Sales Engineer module: it turns unstructured customer requests into structured responses, grounded in your own catalogue, services and prices.

### In this release

- Requests: full envelope extraction with citations, hybrid matching with deterministic fit ratings, clarifications and a structured-only mode that works before you import anything.
- Catalogue: schema-based product data with domain preset schemas, the import wizard, REST pull connections, faceted search and bulk edit.
- Configure (now Design Engineer): configurators with parameter schemas, the formula engine, rules and stock pools with nearest-match.
- Servicing: service definitions and templates, serialised items with QR dockets, the inspection queue and batch servicing in chat.
- Commercial: quotes with versions, branded PDFs and emails, the public acceptance portal, orders, customers and special pricing.
- Billing: a free plan with no card and three paid plans, the ladder that became today's Free, Pro, Ultra and Max.
- Integrations: CSV everywhere, REST connections, signed webhooks and a scoped API.

We publish honest scope. Named ERP and CRM connectors and multi-currency calculation are on the roadmap, stated plainly rather than implied. Inbound email, a roadmap line at the time, has since shipped as the email agent.