Multichannel inventory accounting is one problem wearing several costumes: a physical unit exists in exactly one place at one cost, and five systems disagree about where it is and what it cost. Every question below is a variation on that. The answers that work all point the same direction, which is a single unit-level record that holds cost and location, with the accounting system receiving summarized entries rather than trying to hold the model itself.
Four things, and they compound.
Identity, because the same unit carries a different identifier on every platform. Location, because stock sits in warehouses you control and fulfillment networks you do not. Cost, because landed cost arrives on invoices weeks after the goods and has to be split across SKUs on different bases. Timing, because settlement periods, refund windows, and receiving delays all fall on different calendars.
Any one of those is manageable. Together they produce an inventory number that nobody can tie to a count.
Somewhere else, feeding the accounting system.
General ledgers are built to hold balances, not unit-level cost layers across five locations with assemblies and in-transit states. Pushed to do it, they either cap out on item counts, collapse cost to a running average, or hold one quantity per item with no location dimension.
The workable architecture is that an inventory system computes cost per unit sold and posts summarized entries to the ledger: cost of goods sold against inventory, with shrinkage, damage, and write-downs going to their own accounts. The ledger stays the ledger.
Yes. You own it until it sells. The fulfillment network is a warehouse you rent, not a buyer.
The practical consequence is that you must be able to value it, which means reconciling the platform's unit counts to your own on a regular cadence and applying your own cost layers, not the platform's estimates.
Neither. A transfer moves value between locations and consumes cost layers in FIFO order at the origin. No sale occurred, so no revenue and no gross profit.
The one thing a transfer can legitimately change is unit cost, if you capitalize the transfer freight. Whether you capitalize it or expense it is a policy decision to make once, document, and apply consistently.
Two exceptions worth naming. A transfer between two legal entities is an intercompany sale requiring elimination on consolidation, which is a different problem. And units lost in transit are a shrinkage event, not a costing difference.
They multiply it, incorrectly, unless availability is computed from components.
If a base unit backs a standalone listing, a two pack, and a mixed bundle, and each listing publishes its own availability figure, the total promised across listings can be two or three times the units on hand. Nothing breaks until several listings sell at once, which is precisely what happens during a good week.
Availability has to be derived from component stock at the location that will ship, every time it is queried, and never stored on the bundle record.
At cost, subject to a floor.
FASB Accounting Standards Update 2015-11, *Inventory (Topic 330): Simplifying the Measurement of Inventory*, issued July 2015, requires inventory measured under FIFO or average cost to be carried at the lower of cost and net realizable value. Net realizable value is the estimated selling price in the ordinary course of business, less reasonably predictable costs of completion, disposal, and transportation. The update does not apply to inventory measured under LIFO or the retail inventory method, and it took effect for public entities in fiscal years beginning after 15 December 2016.
Worked on a slow-moving SKU:
| Line | Per unit |
|---|---|
| FIFO landed cost | 22.40 |
| Current selling price after markdown | 24.99 |
| Referral fee at 15% | 3.7485 |
| Fulfillment fee | 6.20 |
| Estimated return and disposal cost | 0.85 |
| Net realizable value | 14.1915 |
Cost of 22.40 exceeds net realizable value of 14.1915, so the units are written down by 8.2085 each. On 2,100 units on hand, that is a write-down of 17,237.85, leaving a carrying value of 29,802.15 against an original 47,040.00.
The write-down is not optional once the condition exists, and it is not reversible under U.S. GAAP if the price later recovers.
Three separate actions.
Record the loss as a shrinkage adjustment at the correct FIFO layer cost, not at an average. File the platform's claim inside their window, which is usually measured in months and does not extend because you were busy. When a reimbursement arrives, credit it against the shrinkage account rather than to revenue, because it is a recovery of a loss and not a sale.
Booking reimbursements to sales inflates the top line and leaves the original loss showing at full value.
Often enough that a variance has a bounded cause.
An annual count tells you that something went wrong sometime in the last twelve months, which is not actionable. A rotating cycle count, with high-revenue SKUs counted monthly and long-tail items twice a year, narrows the window enough to attribute a variance to a receiving batch, a transfer, or a specific facility.
Cycle counts are performed through inventory adjustments inside ConnectBooks, and the audit trail records who adjusted what and when. That record is what makes a variance investigable rather than merely known.
Most sellers at this size do not, and it is worth being clear about why.
Bin and zone detail answers a picking question: where in the building is it? Warehouse-level detail answers the accounting and planning question: which location holds it, at what cost, and can it ship this order? ConnectBooks tracks stock by warehouse rather than by bin or zone, which matches the second question.
If your own facility genuinely needs pick-path optimization, that is a warehouse management problem and a different category of software.
An inventory report answers what you have and where. A valuation report answers what it is worth and is the one that has to tie to the balance sheet.
You need both, plus an aging view, because units and dollars fail in different ways. A count that matches on units and misses on value means your costing is wrong. A count that matches on value and misses on units usually means an offsetting error. Inventory reporting by warehouse, by value, and by aging covers those three views.
Three tie-outs, run monthly.
The valuation report total equals the inventory balance in the ledger. The in-transit value equals the shipments actually on the water and not yet received. Unit counts at each location equal a physical or platform-reported count within a tolerance you have set in advance.
If all three hold, the number is defensible. If any fails, book the difference only after you know what it is. A plug entry to inventory is how a file stops being trustworthy.
Not the part that is broken.
Analysis tools inherit the quality of the ledger they read. A model asked which SKUs to reorder will answer confidently from data that has four aliases for one product and freight sitting in an operating expense account, and the answer will be wrong in a way that reads as authoritative. ConnectBooks offers Crunch, an AI CFO for ecommerce sellers. The order of operations is unchanged: reconcile first, then ask questions.
Stock tracked by warehouse. Bundles, kits, multipacks, and assemblies supported. Transfers held as in transit until received. FIFO valuation with landed cost allocation. Inventory reporting by warehouse, value, and aging. A restock report driven by sales history and velocity, with supplier lead times and inbound stock factored in, though not seasonality. Purchase orders created in the platform and downloadable as PDF, with partial receipts supported, though not emailable to suppliers from inside the system. Cycle counting through adjustments, with an audit trail. Cost of goods and adjustments posting automatically based on settlement data into QuickBooks or Xero.
There is no open external API, so a custom application has to be fed by export rather than by direct integration.
Plans scale by monthly order volume and by marketplace count, and multi-location inventory tracking sits on the Platinum plan. Current tiers and what each includes are on the pricing page. The inventory layer and the channel connections, including TikTok Shop, are where the detail lives.
Running an e-commerce business comes with plenty of challenges, but ConnectBooks is here to make your life easier. With real-time insights, seamless integrations, and detailed tracking of your profitability and inventory, you can stay ahead of the game. Whether you’re selling on Amazon, Shopify, Walmart, TikTok or eBay, ConnectBooks helps you manage your finances with 100% accuracy and confidence, so you can focus on growing your business.
Ready to level up? Start making smarter, data-driven decisions every step of the way. Try ConnectBooks Free Today or Schedule a Demo
