Ecommerce Inventory Management for Small Stores

For a small shop, ecommerce inventory management means the number a shopper sees on your product page matches what is physically on your shelf. Getting there takes three habits: a separate code for every size or shade, automatic deduction with each sale, and a regular count that corrects drift. If you sell cash on delivery, add a fourth: returned items go back into stock only after inspection, not the moment the courier drops them off.

TL;DR: Track stock per variant, not per product. Give each variant a reorder point: average daily sales × supplier lead time in days + a safety buffer. Count your fastest sellers every week. When something sells out, mark it out of stock or pause it rather than deleting the page.

If you are still building the store itself, start with our guide to starting an online store in Egypt and come back here before you upload your first range.

Why ecommerce inventory management is harder than a shop

A shopper in a physical shop sees the shelf. Online, they trust your number completely. When that number is wrong, one of three things happens:

• You oversell. You call to apologise, the customer loses confidence, and sometimes a bad review follows.
• You undersell. The page says "sold out" while units sit in a box, and you never learn about the lost sale.
• You freeze cash. Unsure of your count, you reorder something you already have plenty of.

In Egypt there is an extra layer. A share of cash-on-delivery orders comes back. A unit that left with a courier is not sold yet; it may return in two days, and it may return damaged.

SKUs: every variant is its own product

The most common mistake is counting "matte lipstick" as one product with 40 units. Customers never order "matte lipstick". They order "matte lipstick, shade Brick". Those 40 units might be 25 of a shade nobody wants.

Give every combination its own stock-keeping unit (SKU). Here is a lipstick sold in four shades:

SKU	Shade	Units on hand
LP-MT-NUDE	Nude	14
LP-MT-ROSE	Rose	11
LP-MT-BRCK	Brick	2
LP-MT-PLUM	Plum	13

One listing in the catalogue, four lines in the stock sheet. And the table shows something the total of 40 hides: Brick is about to sell out.

Rules for codes that last

• Short and readable. A few letters for type, finish and variant, as above. A new team member should decode it without a manual.
• Permanent. Never change a code once it has sales history; it is the link between orders and stock.
• Printed on the pack. The person packing orders should not have to guess between two similar shades.

Google treats variants the same way. The Merchant Center guide to item group ID explains that variants of one product are grouped together, while each variant keeps its own data.

Stock states for a cash-on-delivery store

Not every unit missing from the shelf is sold. Split your stock into clear states:

State	Meaning	Available to sell?
Available	On the shelf, ready	Yes
Reserved	On an order awaiting confirmation	No
Out for delivery	With the courier	No
Delivered	Paid and received	No, sold
Returned, pending inspection	Back, not yet checked	No
Restocked	Inspected and sellable	Yes
Damaged	Returned with a fault	No, written off

The state sellers skip is "returned, pending inspection". Put a returned unit straight back on sale and you may ship a stained or incomplete item to the next customer. Inspect first, restock second. The promises you make to customers about returns should match this process; see our guide to an online store return policy in Egypt.

Reorder points: when to call your supplier

A reorder point is the stock level that triggers a new purchase order. The formula:

Reorder point = average daily sales × supplier lead time (days) + safety stock

An illustrative example: a tote bag sells about 4 units a day, and your Cairo workshop needs 6 days to deliver a new batch. You need 24 units to cover the wait. Add a buffer of, say, 6 units in case sales jump or the workshop runs late. When the count reaches 30, you reorder.

Setting safety stock sensibly

• Steady seller, reliable supplier: a small buffer is enough.
• Seasonal item or one you are running ads on: raise the buffer during the season, lower it after.
• Supplier who often slips: increase the buffer, or find a second source for your key lines.

Overbuying has a cost too. Money sitting in slow stock is money that is not funding ads or a new line. To see which items actually earn after delivery and returns, run them through our cash-on-delivery order profit calculation.

The weekly count: thirty minutes that save the month

No system stays accurate on its own. Units get misplaced, packed as the wrong variant, or handed out as samples without being logged. So:

1. Pick your fastest-moving SKUs each week rather than counting everything.
2. Count the shelf and compare it with the number in your store.
3. Record the gap and the reason: damage, sample, data-entry error or unknown.
4. Correct the store figure straight away.
5. Once a month, or after a big sale, do a full count.

If "unknown" keeps appearing against the same SKU, the problem is usually in packing: someone is picking the wrong variant. Printing the code on the pack fixes much of that.

When something sells out, don't delete it

The instinct when an item runs out is to remove it. That throws away two things: a page that may have started to appear in Google, and a customer who might have waited.

The Merchant Center guide to the availability attribute describes it as a real-time signal of whether an item is in stock, out of stock, on preorder or backordered. It explicitly advises against deleting an item you are pausing temporarily, because a deleted offer takes a significant amount of time to show again. The same states appear in the schema.org ItemAvailability vocabulary that search engines read from product pages.

If you sell the same items on more than one channel, the figure must be the same everywhere or you will sell the last unit twice. That problem is covered in marketplace sync for Egyptian stores.

How Baseet does this

On Baseet, stock is deducted automatically with every sale, and you get an alert before a product runs out, so the reorder happens on your schedule rather than after a disappointed customer calls. If you have a large range, you can import all your products from Excel in one go instead of entering them one by one. Starting is free, with no credit card.

FAQ

What is the simplest ecommerce inventory management setup for a small store?

A code for every size or shade, a store that deducts stock with each sale, and a weekly count of your top sellers. That covers most small stores long before a separate warehouse system is needed.

When should a returned item count as stock again?

After inspection, not on arrival. Sellable units go back to available; faulty ones are logged as damaged and removed from the count. That way a problem item never reaches a new customer.

How do I calculate a reorder point?

Multiply the item's average daily sales by the number of days your supplier takes to deliver, then add a safety buffer. When stock falls to that number, place the next order.

Should I delete a product when it sells out?

No. Mark it out of stock or stop accepting orders for it. Google's Merchant Center guidance advises against deleting items you are only pausing, because they take a long time to reappear once removed.

Do I need separate inventory software alongside my store?

If you sell only online from one stockroom, the store is usually enough. Dedicated software starts to make sense with several branches or warehouses, or when you sell wholesale and retail from the same stock.

Written by Sara Mahmoud, E-commerce Strategist at Baseet. Last updated: 16 October 2026.

Let your store do the counting and warn you before a line runs out: start your store on Baseet for free.