How to Manage Inventory in Airtable for a Small Store
Inventory is one of those things that feels manageable when you have thirty SKUs and becomes a quiet crisis when you have three hundred. Expensive inventory software promises to solve this, but for a small store or solo operator, the complexity and cost rarely make sense. Airtable inventory management sits in the right spot: flexible enough to fit your actual operation, simple enough to maintain without a dedicated system administrator, and free or cheap depending on your scale.
What follows is a practical setup for a small store — physical or digital — that wants to track what it has, know when to reorder, and get alerted before it runs out. No custom code, no complicated integrations. Just a well-designed base that tells you what you need to know when you need to know it.
Build your Products table with the right fields from the start
The foundation is a single Products table where each row is a SKU or product variant. Get the field structure right early, because retrofitting fields into a populated base is tedious. A solid starting set:
- Product Name — the human-readable name, plus variant if applicable (Color: Blue, Size: M).
- SKU — your internal identifier. Keep this consistent and never change it once set.
- Category — single-select for filtering and grouping.
- Current Stock — a number field. This is the number you will update when inventory changes.
- Reorder Point — the threshold below which you need to act. Set this per product, not as a global value.
- Reorder Quantity — how many units to order when you restock. Saves calculation time at the moment of reorder.
- Supplier — a linked field to a Suppliers table, or just a text field if you have few suppliers.
- Unit Cost — what you pay per unit. Useful for calculating inventory value.
- Selling Price — optional but useful for margin calculations.
- Notes — lead time, storage notes, anything that does not fit elsewhere.
Two fields do the most work here: Current Stock and Reorder Point. Everything else supports them.
Create a low-stock view that shows you exactly what needs attention
The default grid view shows all your products. That is useful for editing but not for daily operations. What you want is a filtered view that shows only products that need action right now.
Create a new view called Low Stock. Add a filter: Current Stock is less than or equal to Reorder Point. Sort by Current Stock ascending so the most critical items appear first. Hide all fields except Product Name, SKU, Current Stock, Reorder Point, and Reorder Quantity.
This view is your daily opening check. If it is empty, you are fine. If it has rows, those rows tell you exactly what to order and how much. You can bookmark it, share it with a team member, or run an automation against it.
For a cleaner visual, add a color-coded formula field: if Current Stock is zero, flag it red; if it is below Reorder Point, flag it yellow; otherwise green. Airtable’s record coloring feature can apply this automatically to the Low Stock view so critical items jump out immediately.
Set up a reorder point that reflects actual lead time
A reorder point is not just a feel-good number. It should reflect how long it actually takes your supplier to deliver, multiplied by your average daily sales rate, with a small buffer. For a product that sells five units a week and takes two weeks to arrive, the reorder point should be around ten units — not three, not twenty.
Most small stores set reorder points by gut feel and then get caught short when a supplier is delayed. Spend twenty minutes looking at your sales history for your top twenty products and set realistic reorder points. Then review them quarterly — your sales velocity changes with seasons and promotions, and your reorder points should follow.
Add a Lead Time (Days) field to your Products table and a Avg Daily Sales field. You can build a formula field that calculates the suggested reorder point: Lead Time multiplied by Avg Daily Sales, plus a safety buffer you choose. You do not have to use the formula directly, but having it visible helps you audit whether your manual reorder points still make sense.
Track inventory movements with a separate Transactions table
If you only update Current Stock as a raw number, you lose the audit trail. You will not know if a stock level changed because of a sale, a return, a shipment received, or a manual correction. For any store that needs accountability, a Transactions table solves this.
Create a Transactions table with these fields:
- Product — linked to your Products table.
- Transaction Type — single-select: Sale, Restock, Return, Adjustment.
- Quantity — positive number for additions, negative for reductions (or use separate fields).
- Date — when it happened.
- Notes — optional, for context on adjustments.
In your Products table, replace the manual Current Stock field with a rollup or lookup that sums all transaction quantities for that product. Now Current Stock is always calculated from the transaction history, not a number someone typed in. Changes require a transaction record, which means you always know why a number changed.
This is more setup than a raw number field, but for any store with more than one person touching inventory, it is worth it. It turns inventory from a guessed state into a documented one.
Automate low-stock alerts so you do not have to check manually
The Low Stock view is useful when you remember to look at it. An automation ensures you never have to remember.
Set up a scheduled automation — daily, before your work day starts — that finds all records where Current Stock is less than or equal to Reorder Point, and sends a summary email or Slack message listing those products. You open your morning with a clear list of what needs ordering, without opening Airtable at all.
If you want to go a step further, create a second automation triggered when Current Stock hits zero — send an urgent alert immediately rather than waiting for the morning summary. Out-of-stock situations are time-sensitive in a way that low-stock situations usually are not, so they deserve a faster notification.
Both automations are simple to build using Airtable’s built-in automation engine: a time or condition trigger, a Find Records action to identify the affected rows, and a Send Email or Slack notification action with the key fields pulled in as variables.
Add an Inventory Value calculation for financial awareness
One number most small store owners do not track closely enough is total inventory value — what the goods on hand actually cost them. In Airtable, this is a single formula field in the Products table: Current Stock multiplied by Unit Cost. Call it Stock Value.
At the bottom of the grid view, enable the Summary Bar for this field and set it to Sum. Now the total inventory value is always visible at the bottom of the table. You can also create a view filtered by Category and grouped by product type to see where your capital is concentrated by category.
This does not replace accounting software, but it gives you a real-time sense of what your inventory represents in dollars — useful when you are making reorder decisions and want to think about cash flow alongside stock levels.
Start with ten products and scale naturally
The temptation with a new system is to build the full version before using it. Resist that. Set up the Products table, the Low Stock view, and one alert automation. Run your ten most important products through the system for two weeks. The gaps will become obvious — a field you need, a view that would help, a filter that does not quite work. Fix those before expanding to your full catalog.
A simple airtable inventory management system that you actually use every day will always outperform a sophisticated one you built once and then quietly stopped maintaining. Get the basics running well first. The rest can follow as your needs grow.
Set up your Products table this week, add your reorder points, and create the Low Stock view. That alone will change how you relate to your inventory — from reactive scrambling to calm, informed restocking. Start with what matters most, and build from there.