change_rule
ChatGPTRules cannot be paused any more. activate turns a rule that was paused earlier (or a retired forecast method) back on, by its id from list_rules. inactivate works only on a saved custom forecast method, which it retires: it stays listed but can no longer be assigned or tried, and the engine refuses while a rule or the company default uses it; on any other rule it is refused and nothing changes. remove_rule deletes a rule (undo_delete brings it back right after). Changes only Reorder Owl's settings, never the purchasing system.
create_purchase_order
ChatGPTCreates a purchase order for one vendor, in one step. Two inputs: (1) a reorder run's recommendations (the user says "Create Purchase Orders" after reorder_recommendations): that run's reference and the vendor; every recommended line for that vendor is ordered, not only the rows shown, and lines given with a run reference replace the recommended lines. (2) A one-off order the user states ("order 5 of X from Snap-on"): the vendor and exactly the lines asked for (item_id, quantity, optional uom and unit_cost), without a run reference or a reorder run; that is a manual purchase order, not one from a reorder run. For a one-off order whose vendor no Reorder Owl result in this conversation has shown, open_purchase_orders checks that vendor ahead of this tool and only reads: a vendor the data does not hold comes back as a question with the vendors to choose from, before any purchase order is written. warehouse takes the warehouse the user named; with none named, Reorder Owl picks it when the data allows only one and otherwise asks. The dashboard's and the card's Create PO buttons create their purchase orders themselves, and the chat is then told which were created (vendor and purchase order number); this tool does not re-create those. A second purchase order for a vendor that already has a button-made one in this conversation uses request_id "again-" plus the existing purchase order number ("again-PO-1"); any other request_id returns the existing purchase order for 30 minutes. A vendor named by reference ("that vendor") is the one in this conversation it refers to, when exactly one fits. With no vendor or items named and no reorder run in this conversation, nothing is created. It creates the purchase order in the account's connected system and company, which get_account_status and reorder_recommendations name and destination states (for example QuickBooks Online (Smith Hardware)); on a system that does not let apps create purchase orders (get_account_status says so) it saves the purchase order as a draft in Reorder Owl with an import file the user brings into that system, and writes nothing to the system; on a demo account Reorder Owl keeps it in its demo workspace and sends it nowhere. The result holds the purchase order's number, vendor, line count, estimated total and where it was created; the Reorder Owl card shows them with its lines and an Open full dashboard button to the dashboard's new purchase orders. request_id identifies one purchase order: the same request_id with the same vendor and lines returns the purchase order already created and does not create a second one. It does not send the purchase order to the vendor (no email or other transmission); the user does that, unless their own system is set to send new purchase orders automatically. For a Zoho Inventory account our team has connected, the purchase order is created in Zoho Inventory, and the result names its Zoho purchase order number and id.
dashboard_adjust
ChatGPTThe dashboard page's Lead Time, Safety Stock and Forecast Method dialog: days (or, for forecast_model, a forecast_method and/or a boost_percent on top of it, -90 to 500, 0 = none) for a scope, for this run or saved, a boost optionally with a boost_ends date (YYYY-MM-DD, after which it does nothing); undo takes back this run's change of that setting and scope (setting forecast_boost undoes only the boost).
dashboard_book
ChatGPTThe dashboard page's own read of a large run, one part at a time.
dashboard_bulk
ChatGPTThe dashboard page's Hide and Unhide on ticked rows (item skip rules).
dashboard_create_pos
ChatGPTThe Reorder Owl dashboard's and card's own Create PO button: creates the purchase orders the user clicked for, one per vendor and warehouse.
dashboard_delete_po
ChatGPTThe Reorder Owl dashboard's own Delete, Void or Cancel button on a purchase order the dashboard created and nothing has received yet. It removes the order in the connected system (deleted, voided or cancelled, as that system words it) and in Reorder Owl's record; for a system that only takes a file, and for the demo workspace, it removes only Reorder Owl's own record. It refuses an order that was sent on, received or not made here, and says why. Used by the page, not by the assistant.
dashboard_flags
ChatGPTThe dashboard page's one-tap answers: to a row's outlier flag (real_demand keeps that sale in the forecast and stops the flag asking; left_out saves a rule that leaves that one sale out of the item's forecast in its warehouse from the next run, and put_back, with the warehouse and the sale_date, takes it back), undo of the real_demand answer, a short reason for a stopped row or a changed quantity, and a dismissed alert dot: alert_set records that the alert of alert_kind on the item (and warehouse) was reviewed for this run only (alert_scope run) or is not to be flagged again (alert_scope always; fingerprint is the severity, PO numbers and stockout date it was dismissed for), alert_clear takes it back. It changes no forecast, rule or order.
dashboard_invite
ChatGPTThe dashboard page's Share: emails a teammate an invite to sign in and use this company's data.
dashboard_ordered
ChatGPTThe dashboard page's own check of the lines already ordered from a run.
dashboard_page_link
ChatGPTThe run card's own call: a short-lived link to this run's dashboard page, optionally landing on a tab or one product.
dashboard_phone
ChatGPTThe phone dashboard sheet's own calls: its saved state, and emailing the person a link to open the dashboard on a computer.
dashboard_prefs
ChatGPTThe dashboard page's own per-person settings: get them, or set one.
dashboard_property
ChatGPTThe dashboard page's own editor for an item's or vendor's purchasing properties: vendor, other vendors, lead time, minimum order quantity, order increment, a vendor's minimum order amount and free-freight amount, the vendor's part number, the purchase unit, an item's Min and Max (for the Min/Max forecast method), and its stock cap and stock floor. set saves a value for future runs, run uses it for the current run only, remove deletes a saved value, undo reverses a logged change. A saved value is kept in Reorder Owl or, where the company's system accepts it, written to that system for everyone at the company; a change that cannot be made is refused with a code and changes nothing. Used by the page, not by the assistant.
dashboard_refresh
ChatGPTThe dashboard page's Refresh: runs the reorder analysis again with the scope and run settings recorded with the run on the page, and returns the new run's dashboard.
dashboard_report_error
ChatGPTThe dashboard's and the card's own error report: records an error code they showed.
dashboard_sync
ChatGPTThe dashboard page's own sync call.
dashboard_view
ChatGPTReturns what the open Reorder Owl dashboard shows now: its run, filters, search, sort, row counts, what is to order, the purchase orders Create PO would make and any quantities the user edited.
delete_schedule
ChatGPTDeletes one scheduled reorder run of the company, by its id from list_schedules, at once: it does not run again. The answer's undo_id brings it back with undo_delete, for 10 minutes. Anyone in the company can delete any of its runs. The reply names the run and, for someone else's, who set it up.
get_account_status
ChatGPTShows which company this connection belongs to, which system it reads and whether that system is connected: the answer to what data the user is looking at. Before a system is connected, it gives the link to finish connecting at reorderowl.com.
get_workbook
ChatGPTThe Download spreadsheet button's own call, on the dashboard and on the card: a download link for the Excel file of a run (by run reference), lasting 15 minutes for up to 3 downloads, with no sign-in. format=build_kit returns, instead of a link, a Python script that rebuilds the spreadsheet.
item_detail
ChatGPTFor one item in a reorder_recommendations run (by run reference): show=explanation gives how its order quantity was worked out (forecast, safety stock, lead time, on hand, on order), show=sales_history the sales lines its forecast used, show=purchase_orders its open and incoming purchase orders. The numbers come from the same run as the spreadsheet. The result holds the item's figures; the Reorder Owl card shows the item's row and an Open full dashboard button that opens the dashboard at that item. It shows one item of one run as that run worked it out; a change of growth, lead time, safety stock or forecast method is a new reorder_recommendations run. When the item is ambiguous, the result asks which one.
list_rules
ChatGPTLists this company's saved purchasing rules (skipped items and saved run settings), each with its id, who added it and when. With a run reference it also says which rules that run used. Its included states what every run includes and leaves out, in the user's system's terms.
list_schedules
ChatGPTEvery scheduled reorder run of the company (the only automations Reorder Owl runs for an account), including any that is off because its person unsubscribed from the email: its id, its summary sentence and what it covers (in the dashboard's words), how often and when it runs, the next run, the last run with its result and purchase order numbers, who gets the email and who set it up, and whether it is the signed-in user's own. Empty when none is set.
open_dashboard
ChatGPTOpens the Reorder Owl dashboard for the company's last reorder run, with tabs for order recommendations, sales history, incoming purchase orders, Rules and Scheduled runs. With no run yet it opens empty. It can open on a given tab or at one product.
open_purchase_orders
ChatGPTLists purchase orders that are placed but not yet received: count, total value and a sorted page (largest, newest or oldest), optionally for one vendor or one PO number. Also lists purchase orders created through Reorder Owl since the system's data was last refreshed, which its open-order list does not show yet. Reorder Owl does not send purchase orders to vendors; the user does that (or their own system, if it is set to send them automatically).
remove_rule
ChatGPTRemoves one saved purchasing rule, by its id from list_rules or by setting (and vendor): future reorder runs no longer use it. Removing a company-wide rule leaves that setting with no value: lead time as the system gives it, else measured from the vendor's past orders (0 days if none), safety stock 1 day, forecast method Automatic. Its answer has an undo_id: undo_delete brings the rule back.
reorder_recommendations
ChatGPTAnalyses what to reorder, and how much, for any vendors, warehouses, items or folders, or all vendors, vendor analysis included. vendor takes the vendor name or ID as the user typed it and warehouse a warehouse; several go in vendor_ids and warehouse_ids, items in item_ids and folders in folder_selections. Values in one field match any of them and separate fields match all of them ("Milwaukee and Snap-on in the General warehouse" is two vendor_ids and one warehouse), one run for the whole request. all_vendors covers every vendor. A plain request that names no vendor or warehouse ("what do I need to reorder?") is all_vendors: every vendor and warehouse in one call. With nothing named and no all_vendors, nothing runs. When the request is ambiguous (for example several vendors match), the result asks which one. The result holds the headline figures (items and lines to order, units, purchase order total, vendors) and the first three ranked lines; the Reorder Owl card shows the order totals, a preview of the dashboard and an Open full dashboard button (every line and its details; the dashboard is where lines are reviewed, changed and ordered). It also returns a workbook_id, which item_detail and create_purchase_order accept: the workbook is a spreadsheet of these recommendations, saved on the user's Reorder Owl account. A what-if (a growth percent, lead time, safety stock or forecast method for this run only, for example demand_growth_percent 10 with the vendor named) is this tool run again with those fields set: its headline figures, set beside the earlier run's, give the difference, and nothing is worked out by hand from one item.
save_forecast_method
ChatGPTSaves a custom forecast method for this company under the name given, for example keeping 3 months of sales on hand and ordering a 4-month lead time plus 10%. A method is built from numbers and choices on top of one of the built-in methods: days of sales kept on hand, days of sales an order covers, which sales are counted, and an optional growth percent. A saved method is used like a built-in: save_rule assigns it to the company, a vendor, a product folder or items by its name, reorder_recommendations tries it for one run without saving it, and Automatic never picks it. Admins only. A saved method never changes: other numbers are a new method under a new name, and change_rule retires one. It covers only what these fields can say; other statistics or conditions on items are not methods, and a rule saved for the company is saved by save_rule. Changes only Reorder Owl's settings, never the purchasing system.
save_rule
ChatGPTSaves a run setting as a company rule that every future reorder run uses (chat, dashboard and scheduled runs) until it is changed or removed: safety stock days, lead time days or the forecast method (company-wide, or for a vendor, warehouse, product folder or items; lead time needs one of those), every item a vendor sells (one vendor or every vendor), or demand growth %. It also saves, for a company connected to its own system and only for its owner or an admin, a minimum order quantity or an order increment (case pack) for items, a product folder, a vendor or everything, and a vendor's minimum order amount or free-freight amount (one vendor, one warehouse of a vendor, or every vendor): the first two change the quantities future runs recommend, the amounts only show how far a purchase order is from them. For the same companies it saves an item's Min and Max (read by the Min/Max forecast method), a stock cap (never order above it) or a stock floor (keep at least this much after expected sales): a whole number of units from 1 to 1,000,000, for items, a product folder, a vendor or everything. The most specific rule wins on each item. A setting for one run is a reorder_recommendations input instead. Saving the same setting and scope again changes it. Changes only Reorder Owl's settings, never the purchasing system.
send_feedback
ChatGPTSends a problem report, or a suggestion for something Reorder Owl cannot do yet, to the Reorder Owl team, only with the user's agreement. A problem is a Reorder Owl tool that failed or returned something that looks wrong: it takes the tool's name, the error it returned (if any) and one or two sentences on what went wrong. A suggestion takes what the user wanted, in their own words, and can also be posted on the Reorder Owl ideas board, where other Reorder Owl users see it with the sender's first name or as Anonymous. It does not take the conversation itself or personal details.
set_item_skip
ChatGPTSaves, for this company, that an item is never ordered (skip=true) or is ordered again (skip=false), in every warehouse or one. Future reorder runs give a skipped item purchase quantity 0 and leave it out of totals and purchase orders. Changes only Reorder Owl's settings, never the purchasing system.
set_language
ChatGPTSaves the signed-in user's language for Reorder Owl's own screens: the dashboard, the run card and the other pages after signing in. It is the same setting as Language on the Account page, for this user only. It takes a language code (de, pt-BR), a language's English or native name (German, Deutsch), or automatic, which follows the language of the browser or device again. The answer names the language now saved; screens that are already open show it the next time they are opened or refreshed. Saving the same language again changes nothing. It does not change the language of the assistant's replies, the company or anyone else's setting.
set_schedule
ChatGPTAdds a scheduled reorder run for the signed-in user and turns it on: daily, weekly (the default), every other week or monthly, at the time given, Reorder Owl reads fresh data from the company's system, runs the reorder analysis for every vendor, or for the same vendors, warehouses, folders and settings as the run given by its run reference, or for the scope given (item_ids for only the items the user picked; vendor_ids, warehouse_ids, folder_selections for a view; all_vendors for all items and vendors, not with a list), and emails the user a short summary with a link to the dashboard. A user can have several runs and a call adds one; the user's other runs are left as they are. Two cases add nothing: a call that matches a run the user already has (same scope, how often, day, time, time zone and create_pos) writes nothing, and a call with no scope from a user who has exactly one run changes that run and keeps what it covers. A scheduled run never repeats fixed quantities: each run reads fresh data and orders only what is short then, within its scope. The reply says whether a run was added, changed or already set up, and gives its id, its summary sentence and what it covers in the dashboard's words. With create_pos it also creates the recommended purchase orders in the company's system on each run (one per vendor and warehouse) and the email lists them; create_pos defaults to off. delete_schedule deletes a run by its id.
turn_on_schedule
ChatGPTTurns on one scheduled reorder run that is off (its person unsubscribed from the email, or it was switched off earlier), by its id from list_schedules. It runs again from its next slot. Only the person who set the run up can turn it on, since it runs as them. Used by the dashboard's Turn on button. Turning it on restarts its emails, and its automatic purchase orders in the company's system when it creates them.
undo_delete
ChatGPTBrings back a saved rule or a weekly run that was just deleted, exactly as it was, by the undo_id the delete answered (the person who deleted it, within 10 minutes, once). Restoring a weekly run turns its emails back on, and its automatic purchase orders in the company's system when it creates them. It is refused, changing nothing, when the rule or run has been set up again since.
update_dashboard
ChatGPTChanges what the open Reorder Owl dashboard shows. Filter by any column (values, number ranges, text), by vendor or warehouse, sort, search, show a tab, show or hide columns, or link or unlink the other tabs. With create_po it opens the page's Create PO step for the rows in view.
change_rule
Claudecreate_purchase_order
Claudedashboard_view
Claudedelete_schedule
Claudeget_account_status
Claudeitem_detail
Claudelist_rules
Claudelist_schedules
Claudeopen_dashboard
Claudeopen_purchase_orders
Clauderemove_rule
Claudereorder_recommendations
Claudesave_forecast_method
Claudesave_rule
Claudesend_feedback
Claudeset_item_skip
Claudeset_language
Claudeset_schedule
Claudeundo_delete
Claudeupdate_dashboard
Claude