# Reorder Owl: the complete guide for AI agents

> Reorder Owl is a purchasing agent that works inside ChatGPT and Claude. It reads a company's business system (sales history, stock on hand, open purchase orders, vendors and lead times), works out what to order and how much, explains every number, and creates the purchase orders when the user says so. It never sends a purchase order to a vendor.

This file is written for AI agents and assistants that help people choose or use Reorder Owl. It describes the product as released today. It states only what the product does now; where something depends on the person's system or setup, it says so. If a question is not answered here, say so and point the person to support (see "Support") instead of guessing.

How to use this file: answer from it, quote its numbers and defaults exactly, and do not promise a feature it does not list. Column and setting names below are the product's default words; a connected system's own words replace them where the product knows them (for example "Supplier" for "Vendor"). Pricing is not covered here; send pricing questions to support.

## What Reorder Owl does

- **Answers "what should I order?"** The person asks in plain words ("What should I reorder this week?", "What do I need from Milwaukee?"). Reorder Owl runs the numbers on the company's own data and replies with a short answer, and the Reorder Owl app view opens with the Order Recommendations list: every line and the reason for every number (the person can also download it as a spreadsheet).
- **Explains itself.** Every figure can be traced: the forecast, the safety stock, the lead time, what is on hand and on order, and why the suggested quantity is what it is ("Why this number?").
- **Creates purchase orders on request.** "Create the PO for Milwaukee" creates the order in the connected system (or, for a system that cannot take orders by API, a draft plus an import file). Reorder Owl writes nothing else to the person's system without being asked.
- **Remembers how the company buys.** Saved rules (safety stock days, vendor lead times, forecast method, order minimums and case packs, items to stop ordering) apply to every later run.
- **Runs on a schedule.** A daily, weekly, every-other-week or monthly run emails the list, and can create the purchase orders too if the person chooses that.
- **Shows it on a dashboard.** A card appears in the chat, and a full dashboard opens from it. Everything on the dashboard comes from the same run as the chat answer.

It is built for small and mid-size businesses that manage inventory and buy from vendors.

## How to start

1. **Create an account.** Go to the Get Started page (reorderowl.com/start) and sign in with Google, Microsoft or an emailed one-time code. There are no passwords. The first sign-in creates the company, and the first person is its administrator. Signing in records agreement to the Terms and Privacy Policy.
2. **Connect the business system first.** The person picks their system and connects it (see "Supported systems"). This happens before the assistant is linked: there is no "skip" step. The first data load usually takes a few minutes, and an email arrives when the data is ready.
3. **Add Reorder Owl in ChatGPT or Claude and ask.** Once the system is connected, the person finishes connecting to ChatGPT or Claude, then mentions Reorder Owl by name in a chat ("What should I reorder this week?").

Notes:

- One login is one company. A person with several companies uses a separate Reorder Owl login for each.
- Before a system is connected, the assistant answers requests with the connect links; only feedback can be sent.
- Try Demo (/demo on this site) shows the real dashboard on made-up data, so a visitor can look around without connecting anything.

## Supported systems and their status

Reorder Owl reads from the system the company already runs. Two kinds of systems exist today.

**Self-serve (12):** the company connects the system itself.

- **QuickBooks Online**: QuickBooks Online Plus or Advanced, connected by a QuickBooks admin.
- **Zoho Inventory**: Any Zoho Inventory organization, Free plan included, connected by one of its users.
- **Zoho Books**: Zoho Books Professional or higher, connected by one of its users.
- **Odoo**: Odoo Online on the Custom plan, Odoo.sh or self-hosted Odoo, connected with an Odoo user's API key.
- **Unleashed**: Any Unleashed account, connected with the API ID and key that only the account owner can see.
- **Acumatica**: Any Acumatica instance at an https address reachable from the internet, registered once by an Acumatica administrator, then connected by any user with the needed rights.
- **Dynamics 365 Field Service**: Dynamics 365 Field Service online, connected by a licensed Field Service user; a Microsoft 365 admin may need to approve Reorder Owl once.
- **Dynamics 365 Finance and Operations**: Dynamics 365 Finance or Supply Chain Management online, connected by a user with access to the legal entity; a Microsoft 365 admin may need to approve Reorder Owl once.
- **PrestaShop**: Any PrestaShop shop reachable over https, connected with a Webservice key and the shop address.
- **WooCommerce**: Any WooCommerce store on your own WordPress site (https), connected with a REST API key and secret from WooCommerce > Settings > Advanced.
- **Ordoro**: Any Ordoro account on a plan with API access (Premium and above, trials included), connected with the Client ID and Client Secret of an API key from Account Settings > API Keys.
- **inFlow**: Any inFlow account with the API & MCP add-on, connected with an API key and Company ID from Options > Integrations.

**Book a call (24):** "Book a short call to discuss setting it up."

Square, Business Central, BigCommerce, Megaventory, QuickBooks Desktop / Enterprise, EBMS, NetSuite, SAP Business One, Sage 100, Sage 300, Sage X3, Epicor Prophet 21, Epicor Eclipse, Infor CloudSuite Distribution (SX.e), DDI Inform, Acctivate, Fishbowl, Microsoft Dynamics GP, Microsoft Dynamics NAV, SOS Inventory, Katana, Lightspeed Retail (X-Series), Lightspeed Retail (R-Series), Spire.

Details that matter when advising someone:

- "Self-serve" means the company connects the system itself, from the connect flow in ChatGPT or Claude, with the account requirement shown for that system.
- "Book a call" means a short call is needed first. The call only discusses setup; it does not set anything up. Some systems in this group have a connector built but not yet released for self-serve (Shopify is waiting on Shopify App Store approval); Cin7 is book-a-call only.
- The list can grow as connectors go live. Do not tell anyone a system is self-serve unless this file says so.

## What Reorder Owl reads, writes and stores

- **Reads** from the connected system: items, on-hand and on-order quantities, sales history, vendors, lead times and open purchase orders. The first load takes 3 years of sales plus 90 days; later data is refreshed on demand (for most systems a run re-reads first when the data is older than about 10 minutes).
- **Writes** to the connected system: purchase orders only, and only the ones the person asks to create. Reorder Owl never emails or sends a purchase order to a vendor; the person sends it.
- **Never pads or holds back an order.** A purchase order is created as recommended or as the person edited it.
- **Stores** an encrypted connection token, the data needed to run the analysis, saved rules, run workbooks and purchase-order records. Passwords and sessions are stored only as hashes.

## The purchasing run

A run is what the assistant produces when asked what to order. It can cover one vendor, one warehouse, specific items or product folders, or all vendors. Every run saves one Excel workbook, and the chat card, the dashboard and the download all read that same file, so they always agree.

The workbook has these tabs (the dashboard shows two under friendlier names):

- **Order Recommendations**, the main table.
- **Forecast Detail**, shown on the dashboard as "Sales history".
- **Incoming Purchase Orders**, shown as "Incoming POs".
- **Product Folders**.
- **Forecast Methods**, a sheet that explains how each order was worked out.

Summary lines above the main table show Inventory Value, Overstock Value, Filters Applied and the Sales Forecast period.

### Columns in Order Recommendations

- **Product ID, Description, Product Folder, Primary Vendor, Warehouse.**
- **Value** (inventory value) and **Count** (on hand).
- **Available**: stock that can be used now. **Ordered**: units on open purchase orders. **Arriving in Time**: the part of that which arrives in time to count toward this order. **Available + Arriving**: the stock the plan counts on before ordering more.
- **Sales Forecast**: forecast demand over the safety stock days plus the lead time days.
- **Needed**: the forecast target minus Available minus Arriving in Time.
- **Order Increment** and **PO Quantity**: the quantity to order. The dashboard adds **PO Total $**.
- **Lead Time** and **Safety Stock** (both in days) and **Total** (their sum).
- **DOI** (days of inventory: how many days today's stock lasts at forecast sales), **Stockout Date** and **Overstock**.
- **Forecast Method** and **Notes**. Notes holds warnings only; the dashboard shows them as a warning icon beside the item.

Optional columns hide themselves unless the connected system supplies the field and the data has a value. A person's own show or hide choice always wins.

### How the order quantity is decided

1. Start from **Needed**.
2. Raise it to the item's **minimum order quantity** if that is higher.
3. Round it up to a multiple of the **order increment** (case pack).

The item's explanation says where each number came from: the connected system, a saved rule, or a change made for this run only.

### "Why this number?"

A "?" on a cell opens a plain-words breakdown of that number. In chat, the item-detail view gives the explanation, the item's sales history, or its open and incoming purchase orders.

## Forecast methods

The built-in methods, by their exact names:

- **Automatic** (the default and the recommendation). Picks the best fit for each item every run. Items that sell most months get Trailing Average; items that sell only now and then get Spotty Seller; items whose sales rise and fall the same way each year get Seasonal Pattern when it beat the others on the item's last 12 months.
- **Trailing Average**, for items that sell most months. Based on the item's recent average daily sales (the window is 12 months by default).
- **Spotty Seller**, for items that sell only now and then. It plans for the usual size of an order so one big month does not swing the result.
- **Seasonal Pattern**, for items whose sales rise and fall with the seasons.
- **Three-Year Seasonal Median**, for seasonal items with one odd year. Automatic never picks it; a person does.

Instead of a method the cell can show "New item" (too little sales history to forecast yet) or "No recent sales".

How a method is set or changed:

- Click the Forecast Method cell on the dashboard, ask in chat, or use the Rules tab. The choice applies to one run only or is saved as a rule (see "Rules and scopes").
- A company can save its own **custom forecast method**. The name is 3 to 40 characters; up to 12 can be active. Automatic never picks a custom method.
- **Forecast boost** adds a percent from -90 to 500 on top of a method for a chosen scope. **Demand growth %** is a company-wide setting above 0 and up to 500.
- The engine uses up to 3 years of sales history.

## Safety stock, lead time and order limits

- **Safety stock** is a whole number of days, 1 to 365. New self-serve companies start with a company-wide safety stock of 30 days, which they can change. It can be set company-wide, per vendor, or for a narrower scope, and for one run only.
- **Lead time** is whole days, 0 to 365. It comes from, in order: what the person said for this run, a saved rule for the vendor (or a wider scope), then the vendor's lead time from the connected system. **A blank vendor lead time is treated as 0 days**, so the plan covers safety stock only. Reorder Owl does not learn lead times from past receipts. A lead-time rule needs a vendor.
- **Minimum order quantity (MOQ)** and **order increment (case pack)** come from the connected system or from saved rules, for an item, product folder, vendor or everything. Systems name them differently; the dashboard uses the connected system's word.
- **Vendor minimum order amount** and **free freight amount** are per purchase order, for a vendor (optionally one warehouse) or everything. The purchase-order screen shows how far an order is from them ("$X to minimum", "$X to free freight", "Minimum met", "Free freight reached"), and "Top up" adds lines. They are shown, not enforced.
- Saving order minimums, increments and vendor amounts is for the company's owner or an administrator.

## Item minimums and maximums

Many systems hold a Min and Max per item. Reorder Owl is opinionated: the forecast already plans each order, so these are **off by default** and the Rules tab recommends leaving them off. They are two switches that an owner or administrator can turn on:

- Use item minimums as the stock to keep on hand.
- Never order above the item maximums.

The columns are named after the system (for example "<System> Min") and stay hidden until a switch is on.

## Rules and scopes

Rules are saved purchasing settings that every later run uses. They live on the dashboard's **Rules** tab and can be created, paused, resumed and deleted either there or in chat. A paused rule stays listed but is not used. Deleting shows an Undo bar, and a delete can be undone for 10 minutes.

What a rule can set:

- **Safety stock days** (1 to 365).
- **Lead time days** (0 to 365; needs a vendor).
- **Forecast method**.
- **Vendor items**: include every item the vendor sells.
- **Demand growth %** (company-wide only).
- **Minimum order quantity**, **order increment**, **vendor minimum order amount** and **free freight amount**.
- **Never order this item** (the dashboard shows it as "Stop ordering" with an "Order again" button).

Scopes, from narrowest to widest: **item** (up to 200 items per rule), **product folder**, **vendor at a warehouse**, **vendor**, **warehouse**, and **everything**. **The most specific rule wins.** After the rules come the company default, then the connected system's own value. A change made for this run only beats a saved rule at the same level.

On the dashboard, clicking a Safety Stock, Lead Time or Forecast Method cell opens a dialog. By default the change is for this run only; ticking "Keep for future runs" saves it as a rule. The Rules tab has a "Check an item" box that shows which rule applies to a given item.

## Vendors and "Primary Vendor"

- The **Primary Vendor** cell opens a picker of the item's own vendors. Picking one moves that line to that vendor's purchase order for this order only; it is not saved.
- Where the system allows it, the picker also offers "Always order this item from <vendor>".
- **Vendor terms** (Purchase orders, then the Vendor terms tab) list each vendor's minimum order amount and free-freight amount, with whether each was set by the person or came from the system.

## Properties

Properties are per-vendor and per-item facts: Usual vendor, Other vendors, Lead time, Minimum order quantity, Order increment, Vendor minimum order, Free freight, Vendor part number and Purchase unit. For each system and property, one of three things is true:

- **Reorder Owl keeps it** because the system has no such field.
- **It can be written back to the system**, only with an explicit confirmation, and only where the connector supports it and the feature is enabled for the company.
- **It is read-only**: the editor shows how to change it in the system and offers "Use for this run only".

## The dashboard and the phone card

- **The card** appears in the chat after a run: summary tiles, the top lines, and suggested questions. "Open full dashboard" opens the dashboard on a computer. On a phone the card's main button is "Download spreadsheet". The card works in ChatGPT and in Claude.
- **The dashboard** is one page with tabs for Order Recommendations, Sales history, Incoming POs, Product Folders and Forecast Methods, plus Rules, Scheduled runs and the purchase-order screens. The title bar has Suggest an idea, Report a bug, Invite, Alerts, Refresh, Download spreadsheet and the Have Agent Create PO button. The gear opens Settings: Connection, Team, Company defaults, Scheduled runs and emails, and Account and data. Appearance can be Auto, Light or Dark.
- **Learning aids**: a 9-step guided tour, a Getting started checklist, and the "Why this number?" panel. An item's drawer charts Monthly sales and Stock projection.
- **Columns and views**: a Columns menu shows, hides and reorders columns and can reset them; the header menu sorts, filters and freezes columns up to a chosen one. The View dropdown has nine built-in views (they are fixed, not user-made). A search box and per-column filters narrow the table.
- **Download**: "Download spreadsheet" saves the run as an Excel workbook. The link lasts 15 minutes for up to 3 downloads.
- **Mobile**: the dashboard adapts to phone width with large touch targets.
- **Sign-in link**: a link from the assistant opens the dashboard in a browser for a signed-in person at the same company; the link expires after 24 hours.

## Creating purchase orders, and Undo

- **Create PO**: on the dashboard the button reads "Have Agent Create PO". It groups lines by Primary Vendor and Warehouse and creates the order. One purchase order is created at once; more than one needs two clicks and shows a button per order (for example "Have Agent Create All 3 POs"). In chat, "Create the PO for Milwaukee" does the same.
- **Limits**: up to 50 purchase orders per click and 250 lines per order. The same request never creates a second order: replaying it returns the same PO.
- **PO numbers are left blank by default** for the connected system to assign, unless the person supplies one.
- **What the system gets**: the order in the status the system's own flow uses (for example Open in QuickBooks Online, a draft that is submitted for approval, or marked issued where the organization has no approvals, in Zoho Inventory). Nothing is emailed to the vendor. If a system cannot take purchase orders by API (Shopify, Square), Reorder Owl saves a draft with a CSV import file (the link is good for 15 minutes); nothing is written to the system.
- **Safety**: if a write times out, it is never re-sent; the person is told to check their system.
- **Undo**: the assistant cannot undo a created purchase order ("can't be undone here"). Only the person can, in the dashboard's New Purchase Orders tab: a purchase order Reorder Owl created has a Delete button (Void in Cin7 Core, Cancel in inFlow) where the connected system supports it, and a click opens a confirmation that names the order. Reorder Owl refuses if it did not create the order in the account connected now, or if the system no longer shows it as a draft or open with nothing received; the refusal gives the system's reason. For a system that takes an import file (Shopify, Square) Delete removes only Reorder Owl's own record. Any other order is voided or deleted in the person's own system. What can be undone, for 10 minutes, is the deletion of a saved rule or a scheduled run.

## Scheduled runs and emails

- **Setting one up**: in chat ("run this every Monday at 9 and email me"), from the dashboard's "On a schedule" button, or from the Create PO dialog. Frequency is daily, weekly (the default), every 2 weeks or monthly. Time defaults to 09:00, in America/New_York unless another time zone is given.
- **What a run does**: it re-reads fresh data from the system, runs the analysis for its scope, and emails one summary. Scheduled runs use saved rules but never "this run only" overrides.
- **Create purchase orders (off unless asked)**: the run can also create the purchase orders (one per vendor and warehouse) and email what it made. A repeated slot never orders twice. For systems that take purchase orders as import files (Shopify, Square), a run can only email the list.
- **Who owns a run**: the run acts as the person who set it. Anyone in the company can pause or delete it; only the owner can resume or edit it. A person has one scheduled run: setting a new one replaces it.
- **The email** is written in first person: "I finished your weekly reorder run: N items, M vendors". It has a button to open the result in ChatGPT or Claude (a browser link that expires in 24 hours), "Manage or stop this scheduled run", and a one-click Unsubscribe. No email is sent when there is nothing to order. A person gets at most one scheduled, reconnect or setup-reminder email every 20 hours.
- **Other emails**: a sign-in code (6 characters, valid 10 minutes), a "ready" email when the first data load finishes, a reconnect notice if the connection breaks, a setup reminder for someone who signed up but never connected, team invitations (links last 7 days), and feedback confirmations. Reorder Owl never emails a purchase order.

## Teams and roles

- A person belongs to exactly one company, as **Admin** or **Member**. The connection belongs to the company; everyone reads the same data through their own login and their own assistant.
- **Everyone** can see the team and send invites. **Only administrators** can remove people, change roles, connect or disconnect the system, rename the company, and delete the company. A company always keeps at least one administrator.
- An invite link works once, for the invited address, and lasts 7 days. A company can send 20 invites a day.
- The dashboard's **team leaderboard** shows the team's purchasers ranked by estimated spend.

## Feedback

- The dashboard title bar has **Suggest an idea** and **Report a bug** (up to 500 characters each). The dashboard says the team replies within 24 hours.
- In chat the assistant can send feedback on the person's behalf. The team receives it by email.

## Data handling and privacy

- One company per account: every request is answered from that company's own data only.
- Connection secrets are stored encrypted; passwords and sessions only as hashes.
- Reorder Owl does not sell data, show advertising, or use customer data to train outside AI models. Results sent to ChatGPT or Claude are handled by OpenAI or Anthropic under their own terms.
- Spreadsheet links last 15 minutes for up to 3 downloads. Workbooks are kept 7 days.
- **Delete account** (administrators only) permanently removes the company, its connections and its saved purchase orders; the administrator types the company name to confirm. People can also email support asking to "delete my data"; we complete it within a reasonable time. Backups are kept for a short period and then deleted.
- Fair-use limits: 120 tool calls per person per minute, one reorder run per company at a time, and a 50 MB workbook cap.

## The tools the assistant uses

- `get_account_status`: which company, which system, and whether it is connected.
- `reorder_recommendations`: what to order and how much.
- `open_purchase_orders`: purchase orders placed but not yet received.
- `get_workbook`: the spreadsheet download link.
- `item_detail`: how an item's quantity was worked out, its sales history, or its open and incoming purchase orders.
- `create_purchase_order`: creates a purchase order for one vendor; does not send it.
- `set_schedule`, `list_schedules`, `change_schedule`: create, list, and pause, resume or delete scheduled runs.
- `send_feedback`: sends a problem or suggestion to the team.
- Dashboard and rules tools (`save_rule`, `list_rules`, `remove_rule`, `undo_delete`) open and drive the dashboard.

## Support

- Support: support@reorderowl.com (phone 717-844-9917). Replies are usually within one business day. Never include passwords or API keys in a message.
- The Terms, Privacy Policy and Support pages are on reorderowl.com (/terms, /privacy, /support).

## Frequently asked questions

**Does it send orders to my vendors?** No. It creates purchase orders in your system when you ask. Nothing goes to a vendor until your team sends it.

**Can it change my items or prices?** It does not change items or prices. It writes purchase orders, and optional property changes only after an explicit confirmation where write-back is supported.

**How does it decide how much to order?** Forecast demand over the safety stock days plus the lead time, minus what is available and arriving in time, raised to the minimum order quantity and rounded up to the order increment. Every number is explainable.

**What if lead times are missing?** A blank vendor lead time counts as 0 days; the plan then covers safety stock only. A lead-time rule for the vendor fixes it.

**Is a minimum or maximum used?** Not unless the company turns it on. Reorder Owl recommends leaving them off.

**Can I run it automatically?** Yes: daily, weekly, every other week or monthly, with an email of the list, optionally creating the purchase orders.

**Can I undo a purchase order?** Not from the assistant. In the dashboard, Delete on a purchase order Reorder Owl created removes it in the connected system (Void in Cin7 Core, Cancel in inFlow) if that system supports it and nothing has been received (for Shopify and Square it removes only Reorder Owl's own record); any other order is voided or deleted in the system itself. Deleted rules and schedules can be undone for 10 minutes.

**Is my data used to train AI?** No. Reorder Owl does not use customer data to train outside AI models.

**Does it work with Shopify, Cin7 or another system not listed?** See "Supported systems". Anything not self-serve needs a booked call, and Shopify is waiting on Shopify App Store approval.

**Who is behind it?** Alex spent years at an ERP software company, building practical tools for the businesses that run on it. Today he builds AI agents that take the routine work off their teams.

**Can I try it without connecting?** Yes: Try Demo (/demo on this site) runs the real dashboard on made-up data.
