One inventory across stores, warehouses and channels
The first job of the system is to know what you have and where it is. NetSuite tracks inventory by location, so a retailer can see stock in each store, the distribution center, and any third-party warehouse in one place. Available-to-promise logic then lets channels sell what is truly available instead of what the website last cached.
Decide which locations are allowed to fulfill online orders. Many retailers start by fulfilling only from the warehouse and later enable ship-from-store once counts are reliable, because store inventory is only as accurate as the last count.
Connecting storefronts and marketplaces
Online stores and marketplaces typically connect to NetSuite through integration connectors or middleware. The pattern is consistent: orders flow in, inventory levels and tracking flow out, and product data flows to the channels. The design question is who owns each record. If product titles, prices, and images are edited in the storefront, in NetSuite, and in a product-information tool, they will drift.
- Orders in. Import orders, payments, taxes, and shipping charges with the channel order number as the reference.
- Inventory out. Push available quantities on a short schedule, with safety buffers for fast-moving or marketplace items.
- Fulfillment back. Return tracking numbers and statuses so customers and marketplaces see updates quickly.
Order management and fulfillment
Once an order is in the system, it is allocated, picked, packed, and shipped. Rules for splitting orders, choosing the shipping location, and handling backorders should be written down and tested with real examples. Retailers that skip this step find that customer service becomes the place where order exceptions are manually resolved.
Returns, exchanges and refunds
Returns are a major cost in online retail, and the accounting is rarely simple. A return authorization should record the reason, the condition on receipt, the restock or write-off decision, and the refund method. Inspecting and restocking quickly turns returned goods back into sales, while slow processing leaves inventory sitting in limbo and customers waiting for money.
Explore NetSuite ERP at Cold Sun →Pricing, promotions and tax
Promotions are usually defined in the storefront, but their financial effect must reach the ledger correctly. Decide how discounts, coupons, and gift cards are recorded so margin reports are accurate. For sales tax, requirements depend on where you sell: in Canada, GST and provincial taxes vary by province, and cross-border sales into the United States can create obligations in states where you meet economic thresholds. Confirm your obligations with a tax advisor and use a tax service where the volume justifies it.
Payments, payouts and reconciliation
Payment processors and marketplaces pay out in batches that net fees, refunds, and chargebacks. Finance needs to match each payout to the orders it covers. Load payout reports into the system, record fees as expenses, and reconcile deposits to the bank automatically where possible. Without this, the cash balance and the sales ledger drift apart quietly.
A realistic first 90 days
- Days 1 to 30. Clean the item master, define locations, and decide which system owns product data, prices, and customer records.
- Days 31 to 60. Connect your highest-volume channel first, test order import and inventory export with real orders, and fix the exceptions before adding more channels.
- Days 61 to 90. Add returns, payout reconciliation, and ship-from-store if counts are reliable, then review the first full month of margin by channel.
Pitfalls retailers meet
- Treating inventory as a count, not a process. Accuracy requires receiving discipline, cycle counts, and clear adjustment rules, not just a database.
- Too many SKUs at launch. Loading every legacy item, including discontinued ones, clutters search and planning. Migrate only what sells or is in stock.
- Channel logic in several places. If order rules live partly in the storefront, partly in middleware, and partly in NetSuite, troubleshooting becomes guesswork.
- Ignoring peak season. Load-test integrations before the holiday rush; a connector that works at normal volume can fail at ten times the orders.
