Every Gold Silver Ledger plan has a cap on the number of transactions you can record and the number of inventory items you can hold. Bulk Import sits on top of those caps. A single click can add hundreds of transactions to your ledger, so the math gets significant fast.
This article covers how each row in your CSV counts toward your two caps, where the check happens in the import flow, and what to do if an upload would push you over.
Bulk Import is a Premium-only feature, so the caps in question are the Premium caps. For the full plan comparison, see The three plans compared: Starter, Pro, Premium.
How each row counts toward your caps
There are two separate caps at play, and they count differently.
Transaction cap: Every row in your CSV becomes one BUY transaction in your ledger. A 50-row CSV adds 50 to your transaction count, regardless of the quantities involved.
Inventory item cap: Every unit in the quantity column becomes one inventory item. A single row with quantity: 100 adds 100 to your inventory item count from one transaction.
Worked example: a CSV with 60 rows, averaging quantity: 8 per row, adds 60 transactions and roughly 480 inventory items to your account. Both numbers matter — you can be well inside the transaction cap and still get blocked by the item cap, or vice versa.
The Premium caps
The Premium plan currently allows:
2,000 transactions across your account.
10,000 inventory items across your account.
Both caps apply to your account as a whole, not to any single portfolio. A row that lands in your Personal portfolio counts the same as one that lands in a Trust portfolio — they share the same pool.
How the cap check works
The cap check runs after you click Import, not during the preview. The preview screen validates row formats — dates, prices, product matching, length limits — but doesn't compare your file size against your remaining headroom. That comparison happens at submit time.
If both caps have room, the import commits and you're routed to the Transactions History page.
If either cap would be exceeded, the import is rejected before anything is written to your ledger. Bulk Import is all-or-nothing here too — there's no partial commit that fills your account to the cap and rejects the rest.
The error message you'll see is explicit. It tells you four numbers so you can plan the fix:
Your current count: What's in your account right now.
The new count from the upload: How much the CSV would add.
The combined total: What your account would be at after the import.
Your plan limit: The cap you're up against.
From those four numbers, it's straightforward to work out how many rows or how much quantity you need to trim before re-uploading.
For example, if your current count is 1,900, the new count is 200, the combined total is 2,100, and the limit is 2,000, you'd trim the CSV down to 100 rows (or fewer) to fit your remaining headroom.
Where to check your current usage
Before you prepare a large import, glance at your current usage on the Profile tab of the Settings page. Both your transaction count and your inventory item count are shown there alongside the plan caps, so you can see how much headroom you have in each direction.
Doing this check before you build the CSV — not after you click Import — saves a round-trip. If your account is well inside both caps, you can stop thinking about it. If you're close to either, plan the upload size accordingly.
What to do if you're at or near the cap
A few options, depending on what's in your ledger.
Trim the CSV to fit your remaining headroom. Save a smaller batch and run multiple imports rather than one. Each import has its own preview and its own cap check, so you can pace the rollout.
Delete old or test transactions you no longer need. If you have leftover trial entries from when you were learning the app, or rows you imported in error during an earlier session, the Transactions History page can remove them individually.
Consolidate where it's accurate to do so. If your CSV has multiple rows for what was actually the same purchase order — same product, same dealer, same date — they can be merged into one row with a higher quantity, which reduces the transaction count without changing the item count. Only do this where the consolidated row reflects what really happened.
If you're genuinely up against the cap with a clean, deduplicated ledger, you've crossed into "this is a lot of bullion" territory. There's no tier above Premium today, so the practical move is to keep an eye on the caps and clean up sparingly.
Where to go next
Bulk import overview: The conceptual tour of how Bulk Import fits together as a feature.
Uploading and reviewing your CSV: The preview screen and the click-to-import step where the cap check fires.
Fixing common CSV errors: The other category of import failure — row-level validation flags.
Deleting a buy transaction: How to clear old entries to free up headroom.
I've hit my inventory item limit: Troubleshooting from the other side — when the item cap is the one blocking you.
I've hit my transaction limit: Troubleshooting from the transaction-cap side.