Inventory should be the result of recorded events
A balance should not change without an explanation. It increases when merchandise is received or adjusted upward, decreases with a sale or negative adjustment, and changes location through a transfer. Preserving those events makes it possible to investigate a number that looks wrong.
Waiting until the end of the day to subtract every sale creates a second job and a second chance to forget something. In Salelog, completing the sale connects the product, quantity and location to its movement.
Separate merchandise, money and debt
A customer may buy today and pay next week. Merchandise may arrive before you pay the supplier. That is why these events should remain distinct:
- sale: goods or services provided to a customer;
- receipt: money received from the customer;
- purchase: merchandise received from a supplier;
- payment: money paid to the supplier;
- expense: a cost that does not necessarily add inventory.
The separation explains why sales can rise without the same amount of cash arriving, or why stock can increase while a supplier balance remains open.
Set up the smallest useful workflow
Start with fast-moving products. Define the unit, cost, sale price and storage location. Enter opening inventory once, then use actual operations as the normal source of change. Manual adjustments should explain an exception such as a count difference, not become the daily process.
At the end of the week, compare a physical sample with the report. Review cancellations, partial payments and unusual adjustments. Shortening the time between the real event and its record reduces dependence on memory.
Who is this model for?
It can fit independent retailers, social sellers, resellers, small wholesalers, market vendors and service businesses that track parts or materials. Businesses centered on manufacturing recipes, product variants, lots, expiration dates, ecommerce fulfillment or regulated invoicing should evaluate specialized systems for those jobs.