Custom fields
Stock is never just a number. Track the details that matter to you: lot numbers, expiry dates, serial numbers, colors, bin locations, supplier SKUs, anything. Attach custom fields at the item level (shared catalog facts) or the unit level (per stock line or physical unit), reuse them across your catalog, and show the ones that count as columns in your inventory table.
Start free for a limited time| Item | Stock | Cost | Lot # | Expiry | Bin |
|---|---|---|---|---|---|
| Amoxicillin 500mg | 48 | $0.21 | L-22841 | 2027-03 | A-04 |
| Nitrile gloves (M) | 1,200 | $0.06 | L-90115 | 2028-01 | B-11 |
| Saline 0.9% 500ml | 96 | $1.40 | L-33027 | 2026-09 | A-07 |
Add any field you need
Name a field, type a value. Lot codes, dates, serials, dimensions, warranty terms: whatever your stock actually needs.
Item or unit level
Put catalog facts (color, supplier SKU) on the item. Put stock-line facts (lot, expiry) on each unit. Or allow the same field on both.
Reuse across the catalog
Define a field once and reuse it from a dropdown, so the same detail stays consistent on every item or unit that needs it.
Set them with AI
Ask AI to fill in a lot number or expiry date and it updates the field for you, through the built-in MCP server.
Your inventory, your fields
Every operation tracks something the next one doesn’t. A pharmacy lives and dies by lot numbers and expiry dates. A repair shop needs serial numbers and warranty windows. A retailer cares about color, size and supplier SKU. Generic inventory tools force your details into a “notes” box where they can’t be sorted or scanned. Custom fields give each detail its own home.
Item-level and unit-level fields
Not every detail belongs in the same place. Item-level custom fields describe the catalog SKU itself: color, size, supplier SKU, default bin. The value is the same for every unit of that item. Unit-level custom fields describe a specific stock line or physical unit: lot number, expiry date, received date, condition notes. When you hold three lots of the same product, each unit (or stock line) can carry its own lot and expiry without inventing three separate items.
When you create a field, choose whether it applies to items, units, or both. Reuse the same field names across the catalog so “Expiry” means the same thing everywhere, whether it sits on an item or on a unit.
A few of the things teams track with custom fields:
- Lot & batch numbers (usually unit-level) for traceability and recalls.
- Expiry & received dates (usually unit-level) to rotate stock first-expiry-first.
- Serial or asset tags (unit-level, often with unit tracking) for high-value gear.
- Color, size and variant (item-level) for retail and apparel.
- Supplier SKU, manufacturer part number or barcode (item-level) alongside your own naming.
- Bin or shelf location (item or unit) so anyone can find stock fast.
- Warranty, calibration or maintenance dates (unit-level) for tools and equipment.
Mark the fields you reference most as columns so they show in the inventory table at a glance, and keep the rest on the item or unit detail where they’re a click away. Either way they stay searchable and consistent.