add_inventory_area_items
ChatGPTAdd products and/or recipes to an existing inventory area. Only adds the given items; items already in the area are left untouched, so it is safe to call repeatedly. Provide at least one product or recipe ID, at most 50 combined per call. Only batched recipes can be added.
add_manual_product_price
ChatGPTAdd or replace a dated numeric purchase price for a product. This price feeds current recipe and menu cost calculations; it is not a menu item sell price, a persistent gross/net preference, or inventory-batch costing. A newer finalized invoice or manual price can supersede it. Resolve the product and its existing invoice/manual prices with query_records first. Do not call when the requested effective price already matches. The product, non-negative price, and price unit must be unambiguous before calling: use the product current display unit when the user omits the unit, or query product.unitLayers when they name count packaging such as a case or bottle. Ask one short clarification before calling when candidate products, historical package sizes, or linked invoice item names conflict. Use today when the date is omitted. For multiple products, gather candidates, price history, units, and recipe usage in as few parallel query_records calls as possible before writing.
add_pos_report_item
ChatGPTAdd a line item to a draft POS report.
add_quick_ingredient
ChatGPTAdd one unlinked ingredient line, by name and quantity, to a recipe, dish, or shared add-on. Use it only when no existing product or prepared recipe matches; prefer add_recipe_ingredient or add_recipe_component when one does. The line has no cost until the user links a product or enters an estimate in Spensa, so the recipe stays incomplete for costing.
add_recipe_component
ChatGPTAdd one existing preparation or recipe as an ingredient of another recipe, dish, or shared add-on. Quantities are converted to the preparation's base unit and incompatible unit families are rejected. Use this to make an add-on from a portion of sauce or another prepared recipe. It changes the ingredient list; to offer an optional shared add-on use set_recipe_add_on. Edit or remove the resulting line with update_recipe_ingredient or remove_recipe_ingredient.
add_recipe_ingredient
ChatGPTAdd one purchased product as an ingredient of a recipe, dish, or shared add-on. For add-ons the quantity describes one add-on portion. To use a prepared recipe instead, use add_recipe_component. To offer an optional shared add-on, use set_recipe_add_on.
add_recipe_product_group_ingredient
ChatGPTAdd a product group (interchangeable products such as the same ingredient from several suppliers, brands, or pack sizes) as an ingredient of a recipe, dish, or shared add-on. This is the default way to add a purchased ingredient: the cost follows the average price actually paid for the group in the last 30 days, so it stays correct when the supplier or product changes. Use add_recipe_ingredient for one specific product only when the user explicitly asks for that product, supplier, or brand, when the recipe itself names a brand, or when the product has no group. For add-ons the quantity describes one add-on portion.
add_task_attachments
ChatGPTAttach files uploaded in this chat to an existing task. Copies supported chat uploads into task attachment storage. Only images and PDFs are supported. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
add_task_checklist_item
ChatGPTAdd a checklist item to a task.
add_team_members
ChatGPTAssign people to one team without removing any existing memberships or positions. A person can belong to multiple teams: call once for each requested team. Employees must already have active access to the team location; organization members may also join. If the team has a chat, membership grants chat access. Does not change location access roles or send messages. Verify saved teamMember records afterwards.
add_template_products
ChatGPTAdd catalogue products to an order template at the end of its list, keeping all existing items. All products are added together or none is. To add an item that is not in the catalogue yet, create the product with create_products first. Use edit_template only to replace the whole item list.
answer_checklist_items
ChatGPTFill in items of a handed-out checklist on behalf of the user: tick CHECK items, answer YES_NO, NUMBER, CHOICE, TEXT, attach a chat-uploaded photo, mark not applicable, add a comment, or clear an answer. Answers are saved as the user and can trigger the checklist rules. Only use values the user actually reported; never invent readings. Use complete_checklist afterwards when the user wants it completed. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
approve_pos_reports
ChatGPTApprove draft POS reports and start finalization. Reports must have establishment, period, and catalogue-ready items.
archive_employee
ChatGPTArchive one active employee who no longer works for the company. They lose login access, team memberships, open task assignments and upcoming shifts (removedShiftCount says how many). Past shifts, time records and their employee file are kept, and restore_employee brings them back. To remove a test account or a duplicate completely, archive it first and then use delete_employee_permanently.
clone_order
ChatGPTCreate a new order by cloning an existing order. Copies items from the source order with optional modifications (change quantities, remove items, add new items).
complete_checklist
ChatGPTComplete a handed-out checklist once every required item is answered. Completing checks the "not completed" rules of unanswered optional items and notifies the recipients.
complete_task
ChatGPTSet a task status: mark it complete, cancel it (won’t do), or reopen it to To-do. Use query_records on task first to find the task ID.
create_checklist
ChatGPTCreate a reusable checklist (for example an opening or closing routine) with its items and optional rules. It is not handed out until it is assigned to a location with create_checklist_assignment.
create_checklist_assignment
ChatGPTHand a checklist out at a location on a schedule (daily, on weekdays, or on days of the month), with an opening and due time, who fills it in, and who is notified. If today's slot is still ahead or open, today's checklist is handed out right away.
create_employee
ChatGPTCreate one employee without login credentials and optionally assign location access roles. Login credentials are intentionally managed only in employee settings so passwords never enter assistant history. Use query_records to resolve locations and check for an existing employee with the same name before creating.
create_establishment
ChatGPTCreate a new establishment (location). On paid plans, this can affect billing.
create_inventory_area
ChatGPTCreate a new inventory area template (a named list of products and recipes counted together during a stocktake). This creates the empty area; afterwards add products and recipes with add_inventory_area_items.
create_order
ChatGPTCreate a new order draft. Requires an establishment ID and at least one item. Set supplierId to limit it to one supplier, or use null to combine products from several suppliers; custom items then need their own supplierId. A draft with several suppliers is split into one order per supplier when sent. After creating, offer to send it with send_order.
create_order_from_template
ChatGPTCreate a new order from a PUBLISHED order template. Only templates with PUBLISHED status can be used. Use query_records on orderTemplate to find available templates, or use publish_template to publish a DRAFT template.
create_order_schedule_slot
ChatGPTCreate one recurring order schedule slot: "order from supplier X every <orderDay> at <orderByTime>, delivery on <deliveryDay>". Optionally attach a published order template and enable an alert reminder before order time. Requires CREATE_ORDERS permission. Similar or identical slots are allowed, but billing plan limits may reject the create. If the user names a supplier that does not match any existing supplier in the organization, do NOT silently start creating a new supplier — first surface the list of existing suppliers returned in availableSuppliers and ask whether they meant one of those before offering to create a new one.
create_pos_catalogue_item
ChatGPTCreate a POS catalogue item for an establishment. Use query_records on establishment and posCategory first when IDs are unknown.
create_pos_category
ChatGPTCreate a POS category for organizing POS catalogue and draft report items.
create_pos_subcategory
ChatGPTCreate a POS subcategory under an existing POS category.
create_products
ChatGPTCreate one or more products in the catalog in a single atomic operation (up to 30 per call). Use this for both single and bulk creates. Before creating, use query_records to review the organization's existing product categories and check the supplier catalog for the same product. Assign every new product to the appropriate existing categories when there is a clear match, using only category IDs returned by query_records. Use no categories only when none of the existing categories appropriately match. Reuse an existing product when its supplier article number is exact or slightly damaged and its name and unit agree; do not create when multiple candidates are plausible. Treat a supplier article number as strong evidence, not as authoritative when the product name or unit conflicts. For variable-weight products such as meat, small package-weight differences like 340g and 380g can still describe the same product, while large differences like 200g and 1kg should remain separate unless the catalog evidence clearly supports reuse. For imports with more than 30 valid products, keep calling this tool in batches until every product has been created. Set unitStructure for packaging/measures and orderQuantity + orderUnitReference for the default order amount used when adding this product to orders or templates. For unitStructure, count layers are packaging only and measures use the natural display amount and unit; the tool converts 3 LITER to normalizedAmount 3000 and 0.75 LITER to normalizedAmount 750. New product layers do not have IDs yet: omit unitStructure.layers[].id, orderUnitReference.layerId, and initialPriceUnitReference.layerId; never invent layer IDs. The batch rolls back if any item fails validation. Only provide category IDs and supplier product IDs when known with certainty.
create_recipe
ChatGPTCreate one recipe, menu item, or shared add-on. For add-ons set isAddOn=true, leave batchYield and servingQuantity null, and use sellPrice for the surcharge (0 means free). Add purchased ingredients with add_recipe_ingredient or prepared recipes with add_recipe_component, then offer the add-on on dishes or recipes with set_recipe_add_on. Set taxCategoryId for net sales and margin. Query existing names before creating to avoid duplicates.
create_supplier
ChatGPTCreate a new supplier. Only the name is required. When creating from documents or a list, include each supplier's supported details, such as its phone number and clearly identified order addresses, even if other suppliers lack those fields. Set only unknown or ambiguous fields to null; never invent contact details or delay creation to ask for optional fields. Assign a source customer number only after resolving the corresponding establishment.
create_task
ChatGPTAdd a task to a team task list. Set establishmentId to a location for its list, or null for the company-wide list. Optionally set when it becomes available, its due date, assignee, notes, visibility, checklist items, and chat-uploaded attachments. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
create_tax_category
ChatGPTCreate a tax category for menu items with a tax rate percentage.
create_team
ChatGPTCreate one team at a location, optionally with initial members. Check existing teams at that location first and reuse an exact match. Employees must already have active access to that location; organization members may also join. Creates with Show on schedule on and team chat off. Does not create positions, change access roles or send messages.
create_template
ChatGPTCreate a new order template. Templates define reusable order lists. After creating, add items using edit_template, then publish with publish_template.
delete_checklist
ChatGPTDelete a checklist and all its assignments, so it is no longer handed out. Checklists already handed out and their answers stay in the results. This cannot be undone; to stop it temporarily, pause its assignments instead.
delete_checklist_assignment
ChatGPTRemove a checklist assignment so the checklist is no longer handed out at that location. Past results stay. To stop it temporarily, pause it with update_checklist_assignment instead.
delete_employee_permanently
ChatGPTPermanently delete one archived employee who has no work history, for example a test account or a duplicate created by mistake. Archive active employees with archive_employee first. People with shifts, time records, documents, time off requests, tasks, checklists, orders, deliveries, inventory counts or messages cannot be deleted and stay archived (has_work_history). This cannot be undone.
delete_inventory_area
ChatGPTDelete an inventory area template along with its product and recipe list. Past finalized counts keep their record and are not affected. This cannot be undone.
delete_pos_category
ChatGPTDelete a POS category. Catalogue and draft report items currently using it are unassigned.
delete_pos_report_item
ChatGPTDelete a line item from a draft POS report.
delete_pos_subcategory
ChatGPTDelete a POS subcategory. Catalogue and draft report items currently using it are moved back to the parent category.
delete_recipe
ChatGPTDelete a recipe, prep item, menu item, or shared add-on everywhere, including its ingredient references and add-on assignments. This cannot be undone. To stop offering an add-on on only one recipe, use set_recipe_add_on with available=false instead.
delete_task
ChatGPTDelete a task and its checklist, attachments, and activity history. This cannot be undone.
delete_task_checklist_item
ChatGPTDelete a checklist item from a task.
delete_tax_category
ChatGPTDelete a tax category. Existing menu items assigned to it are unassigned and keep their prices.
delete_template
ChatGPTDelete an order template and its items and sections. Existing orders stay unchanged, and order schedule slots stop using the deleted template. This cannot be undone.
describe_spensa_data
ChatGPTGet permission-filtered query_records instructions and catalogue. Follow nextCursor until null, or filter by an exact entity name.
edit_order
ChatGPTEdit content or settings on a DRAFT or IN_REVIEW order: supplier limit, delivery date, supplier note, status, reviewers, or the full item content list. This replaces item records when items are provided. Never use this to add, rename, delete, or reorder sections, move items between sections, or reorder items. Use update_order_layout for every layout or section request. Editing IN_REVIEW orders requires send permission.
edit_product
ChatGPTEdit an existing product in the catalog. Use query_records on product to find the product first. The product supplier cannot be changed after creation. Set unitStructure for packaging/measures and orderQuantity + orderUnitReference for the default order amount used when adding this product to orders or templates. For unitStructure, count layers are packaging only and measures use the natural display amount and unit; the tool converts 3 LITER to normalizedAmount 3000 and 0.75 LITER to normalizedAmount 750. categoryIds replaces all category assignments when non-null. Only provide IDs when known with certainty. Preserve existing layer IDs, measures, article number, name and order defaults unless changing them is part of the request. Packaging transitions affect historical references and require user confirmation of the specific conversion.
edit_template
ChatGPTEdit order template content or settings: saved automatic item sorting (by category or name, or reset to manual), name, internal note, reviewers, or the full item content list. For sorting settings, use defaultItemSort with items null. To change all templates, paginate query_records on orderTemplate to exhaustion and edit each matching template. This replaces item records only when items are provided. Use update_order_template_layout for section changes, moving items between sections, or manual item reordering. Use quantity 0 when the template should default to Quantities Off.
finalize_invoices
ChatGPTReview and finalize draft invoices. Finalization cannot be undone: it creates or links products, adds them to selected order templates, records purchase prices, and drops incomplete items. Always run mode=review first and ask the user to confirm before mode=finalize. Only draft invoices with supplier, location, and date can be finalized. Finalization uses the saved invoice state, so unsaved edits in an open invoice editor are lost.
generate_file
ChatGPTCreate one Excel, CSV, or plain text download only when the user requests an export. Return the provided authenticated Spensa download link.
get_document_upload
ChatGPTCheck a Spensa upload page and retrieve ready file IDs for document tools.
get_spensa_context
ChatGPTDescribe the connected organization, timezone, and granted access. Does not switch organizations.
link_identical_products
ChatGPTLink catalogue products that are the exact same article, typically the same item sold by different suppliers, so their shop prices can be compared. Only link products with the same brand, product, variant, and size; never link similar or substitute products, and ask the user when that is not certain. Products already linked to others bring their existing identical products along, and a group holds at most 20 products.
merge_pos_catalogue_items
ChatGPTMerge one POS catalogue item into another catalogue item from the same establishment. The target item is kept.
merge_products
ChatGPTMerge a duplicate product into another product of the same supplier. Its orders, order templates, invoice lines, recipe ingredients, inventory counts, manual prices and stock move to the kept product, and the duplicate is deleted. This cannot be undone. Resolve both products with query_records first and only merge records of the same item; different brands, sizes, grades or fresh/frozen variants are not duplicates. The kept product does not automatically override incompatible packaging. If units differ, investigate the structures and source evidence, propose a specific alignment preserving known content, and obtain user confirmation before editing units and merging. To merge several copies, call it once per copy with the same target.
prepare_document_upload
ChatGPTCreate one Spensa upload page for up to ten documents. Ask the user to upload there when chat attachments cannot be passed.
publish_template
ChatGPTPublish a DRAFT order template so it can be used to create orders. Only DRAFT templates can be published. Published templates cannot be unpublished.
query_records
ChatGPTRead organization data with a curated Prisma-like DSL. Use operation findMany, aggregate, or groupBy. Use select only; include, skip, take, raw cursor objects, and numeric offsets are rejected. Use first and after for cursor pagination. Top-level first is optional and must be 200 or lower; nested to-many relation first values must be 50 or lower. Check pageInfo.exhaustive before saying a result is complete.
record_waste
ChatGPTRecord a stock loss — waste, spoilage, a staff meal, breakage, or a giveaway — for one product or recipe at a location, with a required comment explaining why it happened. Records a single item; call it again for each additional item. This does not move stock between areas.
remove_inventory_area_items
ChatGPTRemove specific products and/or recipes from an inventory area. Does not delete the area or affect any other items in it. Provide at least one product or recipe ID.
remove_pos_catalogue_item
ChatGPTRemove a POS catalogue item. Items used by finalized reports are archived instead of deleted.
remove_recipe_ingredient
ChatGPTRemove an ingredient line from a recipe.
remove_task_attachment
ChatGPTRemove an attachment from a task and delete the stored file when possible.
rename_inventory_area
ChatGPTRename an inventory area template.
reopen_checklist
ChatGPTReopen a completed handed-out checklist so its answers can be changed again. A reopened checklist past its due time stays open as overdue.
restore_employee
ChatGPTRestore one archived employee (archivedAt is set) with the locations, roles and employee file they had. Locations they had left before being archived stay removed. Login stays off until it is turned on in employee settings. Use this instead of create_employee when the user wants a former employee back.
send_order
ChatGPTSend an order to the supplier via email using the supplier configured order email language. The order must be in DRAFT or IN_REVIEW status. Requires the supplier to have a non-Spensa order email and the establishment to have a complete address. An order without a supplier is split into one order per supplier and each is sent; if any supplier cannot receive it (supplier_orders_not_sendable), nothing is sent and the result lists each blocked supplier and why. If sending stops part way (split_order_partially_sent), the unsent supplier orders remain as drafts.
set_inventory_area_frequency
ChatGPTSet how often an inventory area is expected to be counted (NONE, WEEKLY, or MONTHLY).
set_product_price_display_unit
ChatGPTSet the preferred unit shown for a product price in product lists, charts and tables, such as price per pack instead of per carton. Resolve the product and its existing unit layers or measures with query_records first. This changes only the price display preference: saved prices, recipe costs, packaging and order defaults stay unchanged. Use add_manual_product_price for a new or corrected price amount; use edit_product only when order defaults or packaging also need changing.
set_recipe_add_on
ChatGPTAssign or unassign one shared add-on on a dish or recipe. Use query_records on culinaryEntity.availableAddOns or menuItemAddOn to inspect assignments, and culinaryEntity.offeredOn to see where an add-on is offered. Repeating the same assignment is safe. This does not add an ingredient, change standard costs, or deduct inventory. For an included ingredient use add_recipe_component; to change the shared surcharge use update_recipe.
submit_feedback
ChatGPTRelay user feedback about the product or assistant experience to the internal feedback inbox. Use this when the user explicitly asks to send feedback or reports a concrete product issue. If the user is only expressing frustration, first ask one short follow-up question about what specifically they did not like, then submit that clarified feedback.
unlink_identical_product
ChatGPTRemove one product from the products it is linked to as the same article. The other products stay linked to each other while at least two remain.
update_checklist
ChatGPTRename a checklist, change its description, or replace its items and rules. Checklists already handed out keep their items.
update_checklist_assignment
ChatGPTPause or resume a checklist assignment, or change its schedule, times, who fills it in, late submissions, or notification recipients. Fields left null keep their current value.
update_employee
ChatGPTUpdate an employee display name or selected location access roles. This applies only the supplied location changes and leaves every other assignment unchanged. A null role removes that location assignment and deletes their upcoming shifts there; removedShiftCount in the result says how many. This tool does not manage login credentials, employee files, pay, scheduling job roles, or deletion.
update_establishment
ChatGPTUpdate an establishment (location) with address, contact info, or other details. Use this when send_order fails due to missing address fields. Required fields for sending orders: street, postalCode, city, country.
update_inventory_area_layout
ChatGPTUse this for every inventory area layout or section request: create, rename, delete, or reorder sections; move items into or out of sections; or reorder items. Query every inventoryAreaItem and inventoryAreaSection page until pageInfo.exhaustive is true, then submit the complete top-to-bottom layout with every item exactly once. Set a new section ID to null so the server creates it. Never invent an ID. This updates existing items in place and never adds, removes, or changes item content.
update_invoice_item
ChatGPTUpdate one draft or finalized invoice line item by exact IDs. Use query_records on invoiceUpload or invoice first to find invoiceUploadId, invoiceId, and itemId. This only edits the target line item; it does not add or delete items and does not edit invoice metadata.
update_invoice_metadata
ChatGPTUpdate the location, invoice date, supplier invoice number, or invoice-level discounts on one invoice by exact IDs. Works for any invoice state the backend allows to be edited; queued and finalizing invoices stay locked. Use query_records first and use update_invoice_supplier for supplier changes.
update_invoice_supplier
ChatGPTAssign an existing supplier to one draft, review, or finalized invoice by exact IDs. Use query_records on invoice or invoiceUpload and supplier first to find invoiceUploadId, invoiceId, and supplierId. For finalized invoices, line items linked to products from the previous supplier are safely unlinked.
update_order_layout
ChatGPTUse this for every DRAFT or IN_REVIEW order layout or section request: create, rename, delete, or reorder sections; move items into or out of sections; or reorder items. Query every orderItem and orderSection page until pageInfo.exhaustive is true, then submit the complete top-to-bottom layout with every item exactly once. Set a new section ID to null so the server creates it. Never invent an ID. This updates existing items in place and never adds, removes, or changes item content.
update_order_schedule_responsibilities
ChatGPTReplace or clear the responsibility tags on one recurring order schedule slot. This changes only responsibilities and leaves its supplier, location, weekdays, times, template, and reminders unchanged. First use query_records on orderScheduleSlot to identify the exact schedule and review its current responsibilities.
update_order_status
ChatGPTUpdate the status of an order. Use for marking sent orders as arrived (COMPLETED) or not arrived, and for moving orders in review back to draft or denying them. Status transitions are validated.
update_order_template_layout
ChatGPTUse this for every order template layout or section request: create, rename, delete, or reorder sections; move items into or out of sections; or reorder items. Query every orderTemplateItem and orderTemplateSection page until pageInfo.exhaustive is true, then submit the complete top-to-bottom layout with every item exactly once. Set a new section ID to null so the server creates it. Never invent an ID. This updates existing items in place, never adds or removes items, never changes quantities or units, and leaves existing orders unchanged.
update_pos_catalogue_item
ChatGPTUpdate a POS catalogue item, including mapping an ADD_ON row to its shared add-on with linkedCulinaryEntityId. Use query_records to find the add-on definition. Use null fields to keep current values and explicit clear flags to clear stored values.
update_pos_category
ChatGPTUpdate a POS category name or color.
update_pos_report_item
ChatGPTUpdate a draft or finalized POS report line item. Use null item fields to keep current values and explicit clear flags to clear values. Finalized rows must remain linked to an existing POS catalogue item. Use query_records on posUpload or posReport first to find item IDs and the report state.
update_pos_report_metadata
ChatGPTUpdate a POS report establishment and/or sales period. Use null fields to keep current values and explicit clear flags to clear values.
update_pos_subcategory
ChatGPTUpdate a POS subcategory name.
update_recipe
ChatGPTUpdate a recipe, menu item, or shared add-on: name, labels, categories, allergens, instructions, or price. For an add-on, sellPrice is its shared surcharge and clearSellPrice removes the manual surcharge; leave batchYield/servingQuantity and isOnMenu unchanged because it has a fixed portion. Changes apply wherever the shared add-on is offered. Use set_recipe_add_on to change which recipes offer it.
update_recipe_ingredient
ChatGPTUpdate a recipe ingredient line — its quantity, name, line-level waste factor, or whether it is a garnish or optional.
update_supplier
ChatGPTUpdate supplier details like name, legal company name, VAT ID, phone number, order email addresses, order email language, or per-establishment customer numbers. Only set contact details when the real values are known; use null when unchanged, and never use placeholders. Use query_records on establishment if you need establishment IDs.
update_task
ChatGPTUpdate a task. Can change title, notes, available-from time, due date, assignee, visibility, status, or destination list. Use query_records on taskAssignee before assigning by name. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
update_task_checklist_item
ChatGPTRename, check, or uncheck a task checklist item.
update_tax_category
ChatGPTUpdate a tax category name or tax rate percentage for menu items.
upload_invoice
ChatGPTUpload an invoice file (PDF, PNG, or JPEG) for processing from files available in the current chat session. The invoice will be processed in the background and products will be extracted from it. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
upload_pos_reports
ChatGPTCreate POS report uploads from files available in the current chat session and start processing in the background. Supports PDF, POS report images, XLS, XLSX, and XLSM workbooks. Use query_records on establishment first if the establishment is ambiguous. Defaults to manual review after processing. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.
upload_template_files
ChatGPTCreate an order template upload from files available in the current chat session and start processing in the background. Supply explicit fileIds or chat attachment files; do not assume access to earlier chat uploads.