Skip to content

Blog4 min read

Edit 500 items without touching a screen: the spreadsheet round-trip

Exporting and re-importing your item list in the Clover dashboard is the fastest way to restructure inventory at scale. When it beats editing on-device, how item groups and variants change the job, and the checks to run before you upload.

The fastest inventory edit is the one you make in a spreadsheet. So is the fastest inventory mistake.

Clover's dashboard lets you export your item list, change it in a spreadsheet, and import it back. For a menu or catalog with hundreds of items, that round-trip can turn an afternoon of tapping into a few minutes of fill-down and find-and-replace. It also means one bad column can reach every item at once, so the speed is worth pairing with a few checks.

What Clover's help article covers

Clover's help article on importing an inventory spreadsheet is short. The steps:

  • Save your spreadsheet as an Excel file (.xlsx). If you're prompted to include a Summary worksheet, select No.
  • Log in to your Clover dashboard and go to Items, then Item List.
  • At the top right, select Options, then Import. The same Options menu is where you Export, Print, or review your Item Settings.
  • Drag and drop the file into the field, or browse to it and select Open. Then select Save.
  • Review your additions and changes in the Inventory app or the Register app.

Clover's last line is the whole workflow: the next time you want to update the inventory, repeat the process. Export, edit, import, check.

What the article doesn't spell out matters just as much. It doesn't list the columns, explain how an imported row is matched to an item that already exists, or say what happens to a cell you leave blank. Find those out on a small test, not on your live list.

When the spreadsheet beats editing on the device

Editing one item at a time is fine for a handful of changes. The spreadsheet earns its place when the same kind of change touches many rows:

  • A price change across a whole section of the menu or catalog.
  • Renaming items to a consistent pattern, so staff and reports read the same way.
  • Cleaning up a list that grew item by item over the years, with duplicates and near-duplicates.
  • Adding a large batch of new items at once, such as a new season's stock.

Example (hypothetical round numbers, not a benchmark): a shop raising prices on 500 items by 5% could spend most of a day opening each one on a device. In a spreadsheet, it's one formula filled down a column, a quick check of the results, and an upload. A formula pointed at the wrong column changes 500 prices just as fast.

Stay on the device for one-off fixes, for anything you need to change mid-shift, and for edits where you want to see the item exactly as staff will see it.

Item groups and variants change the job

Variants are where a flat spreadsheet gets tricky. Clover's developer documentation on items and item groups describes how they're built: merchants use item groups to manage variants of a single item. Its example is a T-shirt group with a color attribute (Red, Blue, Green) and a size attribute (Small, Medium, Large).

The item group is one record. Each attribute, like Size, belongs to the group. Each option, like Large, belongs to an attribute. Each variant is created as its own item tied to the group, and a separate step associates items with their options. A Blue, Large shirt is an item in its own right.

That has two practical consequences for a bulk edit:

  • A price change to "the T-shirt" may really be a change to every variant in that group. Count the rows you expect to change before you upload, and check them again afterward.
  • Structural changes, like adding a new size or splitting a group, involve the group, its attributes and options, and the links between them. Test those on one group before you try them across the catalog, or make them in the dashboard instead.

The same developer page shows that a new item gets some settings by default, including whether it's hidden, its price type, and whether it counts as revenue. If your export includes columns for settings like these, treat them as carefully as price. A wrong revenue setting won't announce itself at the register. It shows up later in your reports.

Checks to run before you upload

  • Export a fresh copy of your item list and keep it untouched. Edit a copy, never the only file you have.
  • Run a small test first: change two or three items, import, and confirm in the Inventory or Register app that exactly those changed the way you expected.
  • Spot-check the columns you changed for formula errors, stray decimals, and text where numbers should be.
  • For item groups, count the variant rows you expect to change.
  • Save as .xlsx, and select No if you're asked about a Summary worksheet.
  • Upload outside busy hours, so you have time to review before the next shift.

After the import

Clover points you to the Inventory app or the Register app to review your additions and changes. Do that on purpose: open a few items you changed, a few you didn't, and at least one variant from each item group you touched. Then read your next sales report with an eye for anything that looks off.

Used carefully, the spreadsheet round-trip is the fastest way to keep a large item list clean. The checks are what keep it from being the fastest way to break one.

If you'd like help cleaning up your Clover item list and tying it back to your books, Gameplan Financials pairs bookkeeping and tax strategy with AI systems work: schedule a conversation.