Help Center

Custom Item Fields

Make items carry exactly the fields your business needs.

What are custom item fields?

Every business tracks different things — a grocery store cares about expiry dates and lots, a parts shop about SKUs and suppliers. Custom fields let the owner pick exactly which fields their items carry, so the editor stays clean and relevant.

Open the sliders icon next to “Add Item” (owners only) to choose from an industry-standard library:

  • SKU, cost price, reorder level & reorder quantity
  • Supplier and supplier SKU
  • Unit of measure, status (active/discontinued)
  • Expiry date, lot/batch number, lead time, brand, model number

Toggles save instantly — no confirm button needed.

Creating your own fields

Need something we didn’t predict? In the same dialog, type a name (e.g. “Wine region”), pick a type — text, number, currency or date — and hit Add. Your field appears in the item editor like any library field.

Where field values show up

Enabled fields appear in a collapsible “Details” section inside Add Item and Edit Item. Only the fields you enabled render — a business with two fields sees two inputs. Values you set are kept even if you later disable a field (they come back when you re-enable it).

Text fields remember what you have used before: click into Brand, Category or any text field of your own and the five most recent values appear underneath, narrowing as you type (“F” offers “Food”). Pick one with Enter or a click and it fills in with the same spelling, so categories stay consistent across items. Numbers, dates and dropdown fields are unchanged.

The little dashed “+” in the editor is a shortcut to the field picker.

Filling fields from a spreadsheet

When you import a spreadsheet, any column whose heading matches one of your custom fields (by its label, ignoring capitals and punctuation) fills that field on every imported item: “Colour”, “Sub category”, “Season”, whatever you named it. The library fields (SKU, supplier, cost price, expiry…) are matched as before. A column called Category fills a custom field named Category if you have one, and still matches a tag of the same name. Create the fields first, then import, and the review screen shows the values each row will carry.

Photos too: a column headed Image, Image URL, Photo or Picture can hold one or more public https links to pictures (separated by commas). After the rows are saved, our server fetches each picture, optimises it and stores our own copy on the item (up to 8 per item), exactly as if you had added it in the item editor, so it shows in the list, in the phone apps and in Square. The import itself runs at full speed. Most pictures appear within the hour; very large catalogues can take up to a day. Links that cannot be read are skipped; the item itself is still imported. Photo links are unlisted: anyone holding the exact link can view a picture, but the links are not listed anywhere and cannot be guessed. Removing a photo takes it off the item, the phone apps, the API and Square right away and the stored file is deleted; copies on our delivery network can remain reachable by the exact link for a limited time afterwards, at most a year.

Already have the items and only want to add their pictures? Import a sheet with the names, barcodes or SKUs and the picture links, and tick “Add photos to matching items” on the review screen: each matching item that has no photo yet receives the links, and nothing else on it changes.

Adding photos to products you already have

You can add pictures to an existing inventory from a spreadsheet without deleting anything, changing anything else, or creating duplicates.

Your file needs:

  • A Name column (the importer needs it to read the file).
  • A picture column headed Image URL (Image, Photo or Picture also work) with public https links, several per cell separated by commas, up to 8 per product.
  • For a safe match, the product’s Barcode or SKU exactly as stored here. Matching tries the barcode first, then the SKU, then the name; barcode and SKU must be exact, and a name must be identical apart from capitals and extra spaces.

Every other column is optional and is ignored for matched rows: quantity, price, description and your fields are not changed.

How to run it: import the file as usual. On the review screen the matched rows show under “Needs attention”; tick Add photos to matching items and press the button, which now reads “Add photos to N items”. Each matching product that has no photo yet receives its pictures in the background (most within the hour, very large catalogues up to a day). Products that already have a photo are left alone.

Check before you press: “Will be added” should read 0. A row that matches nothing is created as a new product, so a name spelled differently from the one in your inventory would become a duplicate rather than a photo. Owners and team members with the edit-items permission can do this.

Large inventories (above 5,000 items): before the review screen shows its counts, every row is checked against your whole inventory on the server (a big file takes a little longer to analyse), so “Will be added” and the photo count are right for every product, not only the ones loaded on the page; the import then re-checks while saving, so nothing is ever added twice. Include a Barcode or SKU column where you can: on older records a name alone may not match.

Filtering the list by a field

Once a field is enabled, the Field button on the inventory list (next to the tag filter) filters by it. Open a field and tick what you want:

  • Select fields (status, unit of measure) list their options as checkboxes.
  • Text fields (brand, supplier, SKU, your own fields) list the values already in use; you can also type a value and press Enter. Matching ignores capitals and extra spaces, so “lego” finds “Lego”.
  • Date fields offer Expired, Expires within 30 days and Has a value. Number fields offer Has a value.

Tick as many as you like. Several values on the same field mean “any of these” (brand Lego or Hasbro); conditions on different fields all apply (brand, and colour, and expired). The button shows how many are active, each one appears as a chip under the toolbar with its own ×, and Clear all removes them in one go. Filters combine with search, the tag filter and Hide Sold Out.

This is how to do categories without using up your tags: create a custom field called Category (or Department, Season, Colour…), fill it in per item or from your spreadsheet, and filter on it. On large inventories the first condition is answered by the server across everything and the rest narrow it as you load more, so the line under the toolbar reads “matches so far”.

Fields + AI: the good part

The AI reads your fields automatically:

  • AI Analyst can answer “what’s my inventory value at cost?” (qty × cost price) or “which lots expire this month?”
  • AI Alerts can watch any field — “alert me a week before anything expires”, “when cost-price items over $100 get scanned out”.
  • The Developer API includes a fields object on every item, so external apps get your SKUs, cost prices and expiry dates too.

And once items carry a Cost price, margins appear everywhere: the inventory list shows a live valuation strip (units in view, value at cost, at retail, and your potential margin), and the item editor shows per-unit margin the moment you type a price.

Reorder level → automatic alert

If you enable the Reorder level field and save an item with one set, we’ll offer to create a matching AI Alert with one click — so you’re notified the moment stock falls to that level. No duplicate is offered if a rule already watches that item.

Batches & lots: why same product, different expiry dates

A standard retail barcode (UPC/EAN) identifies the PRODUCT, not the unit — two cartons of the same milk with different expiry dates carry the exact same barcode. That’s how it works in every grocery store on earth.

Stores handle this with FEFO — First Expired, First Out: newer stock goes behind older stock so the oldest sells first, and batch/lot records track what expires when.

Inventory Inventory has this built in — and it’s completely OPTIONAL. If your business doesn’t deal with expiry dates, you’ll never see it and nothing changes for you. To turn it on, enable the Expiry date (or Lot number) field, open any item, and you’ll see a “Batches / lots” section in the editor. Remove an item’s batches anytime to go back to simple quantity tracking.

How batch tracking works — exactly

Add a batch for each delivery: its quantity, its expiry date, and (optionally) its lot number. From that moment:

  • The item’s total quantity automatically equals the sum of its batches.
  • The item’s Expiry date field always shows the EARLIEST batch expiry — so expiry AI Alerts (“alert me a week before anything expires”) just work, no extra setup.
  • Every deduction — a scan-out, a sale via the +/− buttons, or an external app selling through your API — removes stock from the soonest-expiring batch first (FEFO), exactly like a well-run store rotates its shelves.
  • New stock arriving (restock scans, quantity increases) joins the newest batch. The quantity field in the editor is set by the batch rows while any exist, and the AI Assistant adds stock only to a batch you name.
  • When a batch hits zero it disappears, and the expiry field rolls forward to the next-soonest batch automatically.

Example: Milk has Batch A (6 units, exp Aug 1) and Batch B (12 units, exp Aug 15). A customer buys 8 → Batch A empties, Batch B drops to 10, and the item’s expiry date automatically becomes Aug 15.

Cost per lot: the same part bought at different prices

Hardware, parts and wholesale businesses buy the same item at different prices over time: one delivery at $100 a unit, the next at $120, the one after at $95. With the Cost price field enabled, every batch row in the item editor has a Unit cost column, so each lot keeps the price it was bought at. The editor shows the value at cost and the weighted average cost of what is left, lot by lot; the inventory list’s valuation strip adds up every lot at its own cost; the AI Analyst can answer “what is our stock worth at cost?” and “what did the last lot cost?” from the same figures.

Receiving a purchase order does it for you: when a received line creates a new lot (the item already tracks lots, or you type an expiry date or lot number), the lot takes the order line’s cost price. A lot without a unit cost simply uses the item’s cost price, so nothing changes for items that never had one. Deductions still follow first-expired-first-out, so the cost of the next units out is the cost of the lot that leaves first.

Two things to know. Stock added without a lot (a restock scan, a plain quantity increase) joins the newest batch at that batch’s cost, so a delivery bought at a new price should be received as its own lot. The AI Assistant is stricter: it deducts from the soonest-expiring lot like everything else, but adds stock only to a lot you name (“add 10 to lot B200”) and asks which lot otherwise. And the phone apps edit quantities, expiry dates and lot numbers but not unit costs yet; costs entered on the web are kept when a phone scans or edits the item.

Batch tips: barcodes, alerts and the AI

  • Keep using the product’s manufacturer barcode for scanning — batches are deducted FEFO automatically, so you don’t need separate barcodes per batch.
  • Want to scan a SPECIFIC batch? Create separate items per batch instead (e.g. “Milk 2% — Aug 1 lot”) and print our auto-generated barcodes for each — your choice per product.
  • Full lot traceability: the Activity Log records exactly which lots each deduction consumed (e.g. “Shipped out → quantity 4 — took 6× A123 (exp Aug 1), 2× B200”) — including sales made through your Developer API. If a supplier recalls a lot, search the log for its lot number to see every movement.
  • The AI Analyst sees your batches: ask “which batches expire this week?” or “how much of the Aug 1 milk lot is left?”
  • Removing every batch from an item returns it to simple single-quantity tracking.