Troubleshooting

"A sale shows the wrong profit or cost of goods"

Cause: cost of goods uses the item's weighted-average cost at the time of the sale — not the sale price and not the latest purchase price.

Fix: find the earlier purchase or opening-balance transaction with the wrong unit cost and correct it there — the average recomputes and the margin follows. How the average is built is explained in How Costing Works.

"My production run consumed nothing and didn't add any stock"

Cause: the run itself is not marked Completed. A production run's linked transactions follow the run's status — nothing is consumed and no output is added until the run completes.

Fix: open the run under Create → Production Runs and mark it Completed. Ingredients are deducted and the output is added in one step.

"I can't change a recipe's Target Inventory when editing it"

Cause: this is intentional. The target (along with its category, variant, and batch unit) is locked on existing recipes so that past production runs keep a consistent costed history.

Fix: create a new recipe that targets the other item (duplicating the existing recipe is the fastest start), and archive the old one if you no longer need it.

"The Target Inventory picker is empty"

Cause: the picker only lists items that can be produced — products, services, finished goods, and subassemblies. If you haven't created one yet, there is nothing to show.

Fix: create the item first — for example a product under Deliver → Products or a finished good under Create → Finished Goods — then return to the recipe. Which categories can be made versus bought is covered in Sellable vs Purchasable.

"The ingredient picker won't accept an item I know exists"

Cause: the picker filters ingredients by what the recipe's target allows. A recipe that manufactures a finished good or subassembly accepts raw materials, food, subassemblies, packaging, and MRO; a recipe targeting a sellable product or service also accepts finished goods, labor, other products — and raw materials or food directly.

Fix: check the missing item's category. If it is the wrong kind for this target — for example a product used as an ingredient in another manufactured intermediate — restructure it as a subassembly or finished good, or change what the recipe targets.

"I switched location and my inventory and transactions are gone"

Cause: nothing was deleted. Inventory, transactions, and recipes are tracked per location, so the app shows only the current location's records. The same SKU at two locations has independent counts and costs.

Fix: open the Select Location map-pin dropdown in the top header and switch back to the location you were working in. Read Locations & Entities for how per-location scoping works, and use Optimize → Transfers to move stock between locations.

"My import failed — a required field isn't mapped or a column wasn't recognized"

Cause: every required field (for inventory: Name, SKU, Category, State, Unit) must be mapped to one of your CSV columns in the mapping step, and each CSV column can only be used for one field.

Fix: in the mapping step, assign a column to every field marked required and clear any duplicate assignments. Starting from Download Template in the list's ⋯ menu makes every column match automatically. Full column lists are in the Import Reference.

"Invalid Category, State, Unit, or allergen errors"

Cause: the value isn't one of the accepted values — usually an abbreviation like "g" where the full unit name "gram" is expected.

Fix: use the exact values from the Import Reference tables. Matching is case-insensitive, and near-misses get a "Did you mean?" suggestion right in the error message — apply it and re-upload.

"DefaultEntity not found, or an attribute isn't defined"

Cause: import never auto-creates locations, vendors, attributes, tags, customer groups, or referral sources — every name in your file must match a record that already exists.

Fix: create the referenced records first (for example the vendor, or the attribute and its options under Settings → Attributes), then run the import again.

"Opening stock imported on the item, but the variant shows zero — or stock doubled"

Cause: item-level Quantity and UnitCost and variant-level VariantQuantity and VariantUnitCost each seed their own opening balance. Stock on the item row doesn't attach to a variant, and filling in both levels counts it twice.

Fix: for items with variants, put opening stock in VariantQuantity and VariantUnitCost on each variant's row and leave the item-level columns blank. If an import already double-counted, correct it with an adjustment transaction.

"A generic 'Could not save' or 'Something went wrong' error"

Cause: most often one of two things — the session's account or location went stale (for example after a long idle period), or a numeric field contains formatting the validator rejects, like a thousands separator or a currency symbol.

Fix: check numeric fields first — enter 1234.50, not 1,234.50 or a value with a currency symbol — then save again. If the error persists, reload the page (your form values may need re-entering) and retry.