Clover's native inventory is an item catalog with stock counts — genuinely useful, and narrower than most merchants expect when they go looking for reordering features. What's native: items with quantities, categories, modifiers, variants, and automatic "sold out" handling when stock hits zero. What arrived only in April 2026: native low stock alerts — a per-item threshold that notifies you when the count falls below it (currently North America only). What still doesn't exist natively, on any plan: purchase orders, vendor records, receiving, or any reorder automation — Clover's data model simply has no vendor or PO objects, and Clover's own blog points merchants to App Market apps for ordering.
This guide maps exactly what each Clover plan includes, how to use the new alerts, what the App Market apps add, and where the buying loop actually runs.
What's native, by plan
From Clover's official service-plan documentation:
| Plan | Inventory capability |
|---|---|
| Payments / Payments Plus | None — payments, employees, customers only |
| Essentials | "Simple inventory and order management" — the item catalog with stock counts |
| Register | Adds modifiers, modifier groups, and variants (sizes, colors) |
| Counter / Table Service Restaurant | Register-level inventory plus restaurant features |
Stock is a per-item quantity, managed in the Inventory app and Merchant Dashboard. With auto-manage on, an item marks itself unavailable at zero and comes back when restocked. Practical scale notes from Clover's own community: bulk imports run in the low thousands per file, and merchants are advised to keep catalogs under roughly 15,000 items.
The new low stock alerts (April 2026)
Clover added native low-stock alerting in April 2026: set an alert threshold per item, get notified when the count drops below it, and filter your inventory to low-stock items. Two things to know:
- It's an alert, not a reorder. Nothing computes the threshold for you (it's a number you type and maintain — the same static-threshold problem as every POS), and nothing turns the alert into a purchase order.
- North America only for now, per Clover's own docs.
If you read older reviews complaining that Clover "can't set minimum levels or reorder levels" — that was true until April 2026, and it's now half-fixed: the level exists, the reorder still doesn't.
Ordering: there is no native path
This is the part to be clear-eyed about. Clover has no purchase orders, no vendor management, no receiving workflow, and no cost tracking on replenishment — not as a missing toggle, but structurally: the platform's inventory model contains no vendor or PO objects. Clover's official answer is the App Market, and its own blog recommends ordering apps by name: Thrive Inventory (Shopventory) for retail POs and vendor management, SKU IQ for multi-channel stock sync, MarketMan for restaurant vendor ordering, Yellow Dog for deeper retail purchasing workflows. These are real apps solving real gaps — at a second subscription, with your buying data living in a second system.
So a Clover merchant's actual buying loop is: native alert (or a walk of the stockroom) → an app or a spreadsheet → the vendor's email or portal → receiving against memory → costs nowhere. Each arrow is a manual handoff.
What the layer should do instead
The app-per-gap approach recreates the fragmentation it was meant to fix. The alternative is one procurement layer beside Clover that runs the whole loop: reorder points computed per item from your actual Clover sales velocity and each vendor's lead time — not typed thresholds; suggested orders that respect pack sizes, minimums, and what's already inbound; POs sent per vendor over email, text, or EDI; vendor replies — confirmations, shorts, substitutions, price changes — captured on a living purchase order; receiving reconciled against the confirmed order; and cost history that survives into your accounting.
That's what LineNow runs with Clover — Clover stays the register and the sales record, and the buying side gets an actual system. The structural argument is in the Clover procurement layer guide; convenience and liquor stores (a huge share of Clover retail) should also read how c-store and liquor ordering actually works. Sanity-check your new alert thresholds with the free reorder point calculator — the difference between the number you'd type and the computed one is usually the argument.
Sources checked
- Clover dev docs: Working with inventory (data model: items, stock, categories, variants — no vendor or PO objects)
- Clover dev docs: Managing item availability (auto-manage at zero; stock alert thresholds, NA-only)
- Clover API changelog, April 2026 (low stock alerts launch)
- Clover dev docs: Merchant service plans (per-plan inventory capability)
- Clover blog: How Clover helps retailers manage inventory (App Market apps recommended for the gaps)
- Clover Community: inventory item limits (community guidance, noted as such)