Retail e-commerce management software runs the retailer's own online store as part of the business rather than beside it: the product content that goes on the site, the orders that come back, the picking and packing that follows, the shipment and its tracking, and the returns that arrive by post. With Pentoggle, a retailer can describe how their online channel actually runs and generate the starting application around it.
This page is about your own site. Marketplaces are Marketplace Order and Payment Management Software. The shared stock figure the site publishes is Retail Online-Offline Inventory Software. Collection and shipping from a store are Retail BOPIS and Ship-from-Store Software. Orders in general, including special orders taken in store, are Retail Order Management Software.
Selling online carries obligations that differ from selling across a counter, in areas such as consumer rights, returns and cancellation, information you must provide, and how tax applies to where the customer is. All of that differs by place and changes. This page describes the workflow and states none of it. Establish what applies with your accountant and a suitable adviser.
Most retailers already run an accounting system such as QuickBooks, Tally or Xero, a POS, and a platform for the website itself. Those stay where they are. What is often still managed outside them is everything between the order landing and the parcel arriving: the pick list printed from a dashboard, the tracking number pasted into an email, and the returned parcel sitting unopened in the back.
Key takeaways
- The order is the start of the work, not the end. Much of the cost and many of the failures sit in picking, packing, shipping and returns.
- Product content is an operational asset. Missing or wrong information can produce returns, questions and refunds, and it is often cheaper to fix once than to handle repeatedly.
- Online orders should join the same queue as everything else the store fulfils, so the team runs one process rather than several.
- Returns by post are a workflow with a physical end. The refund is easy; getting the item back into sellable stock, where its condition allows, is where value is recovered or lost.
- A useful number is the share of orders shipped complete and on time, read alongside the online return rate.
The spreadsheet is often not the problem
A small online channel run from the platform's own dashboard, with orders printed and packed by one person, is a working system and a sensible place to start.
The trouble starts at identifiable points.
When the site's stock is its own
The website has its own quantity, updated when someone remembers. It oversells the item the shop floor just sold, or it keeps a permanent buffer and quietly undersells all year.
When picking is a printed page
The picker walks the store with a sheet, cannot find one item, and either substitutes without asking or ships short. Nothing records which, so the customer discovers it.
When status updates are manual
The tracking number is copied into an email when someone gets to it. Customers who were not told email to ask, and answering those emails becomes a job.
When returns arrive as parcels
A box comes back with a note or nothing. Which order it belongs to, whether the item is sellable, and whether a refund is due are worked out later, and sometimes after the customer has complained.
What e-commerce management software holds
Product content
Titles, descriptions, attributes, images and category placement held with the item record, so what appears online comes from the same product the store sells.
Listings
What is published, at what price for this channel, with availability governed by the shared stock rules.
Order queue
Online orders alongside the store's other orders, with a common status model from received to delivered.
Payment and fraud checks
Payment status from your provider recorded against the order, with any hold or review step you want before picking.
Pick and pack
Pick lists sequenced sensibly, scan confirmation of the variant, packing recorded with what went into which parcel.
Shipping
Carrier, service, parcel details and tracking reference recorded against the order, with labels produced where your carriers allow it.
Customer notifications
Confirmation, dispatch, tracking and delay messages triggered by status changes rather than sent by hand.
Online returns
The return request, the item arriving, inspection, destination in stock, and the refund or exchange, linked to the original order.
The order is where the work begins
An online sale looks like a counter sale with a delay. It is closer to a small logistics operation attached to a shop.
Each order needs a person to find the items, confirm they are the right variants, pack them so they survive the journey, generate a label, hand them to a carrier and tell the customer. Every one of those steps can fail in a way the customer sees, and the customer has already paid.
Two failures that tend to cost most are shipping the wrong item and shipping late. The first is a picking control: scanning the variant rather than relying only on a label can reduce picking errors, particularly for size and colour variants. Location accuracy, picker workflow, training and a verification step at packing all contribute as well. The second is a queue control: knowing which orders are unpicked, which are packed and unshipped, and which are past their promised date, so the ones at risk are visible before the customer notices.
Substitutions and shortfalls need a decision path rather than a picker's judgement. Contact the customer, ship partial, hold the order, or cancel the line: each is right in some circumstances, and the rule should be set in advance with the customer informed either way.
Where orders are picked from a shop floor that customers are also shopping in, as many small retailers do, the pick competes with the counter for the same units. That is a stock reservation question, covered on Retail Online-Offline Inventory Software, and it is worth resolving before volume grows.
Product content is an operational asset
The description, the attributes and the images are not marketing decoration. They are much of the information the customer has, and gaps in them often come back as returns and questions.
An item without a size guide can produce size returns. An image that misrepresents a colour can produce "not as described" returns. A missing attribute, dimensions, material, compatibility, can produce emails that someone has to answer one at a time. Each of these can be a recurring cost created once.
Holding content with the item record, rather than only in the website platform, has practical benefits. The same content can feed other channels without being rewritten. A change to a product is made in one place. And the content gaps become visible: items published with no image, no description or missing key attributes can be listed and fixed as a batch.
The feedback loop worth building is from returns. Return reasons by item, as described on Retail Returns Management Software, can point at listings that are misleading. An item with a high "not as described" rate may have a content problem, and where it does the fix is often quick and stops the cost recurring.
Returns by post are a stock workflow
Online return rates are often higher than in-store rates, and the return arrives as a parcel rather than as a customer at a counter, which changes the workflow.
The steps are: the customer requests the return or simply sends it back, the parcel arrives and has to be matched to an order, the item is inspected, it is given a destination in stock, and the refund or exchange is processed.
Matching is where time is lost. A returns note or a reference the customer includes makes it quick; a bare parcel makes it a search. Providing a return reference, and asking for it in the box, is a small thing that can save a great deal of handling.
Inspection decides value recovery. An item that comes back sellable can go back into stock. One that needs repackaging is often worth the few minutes it takes. One that is damaged or used needs a decision: supplier claim, markdown or write-off. Skipping inspection and shelving everything risks sending unsellable items out again.
Refund timing is a service question with obligations attached. What you must refund, within what period, and what you may deduct, differ by place and change, so establish that with a suitable adviser and build the process to meet it.
The stock consequence matters at the business level too. A returned unit may become available again, depending on its condition and destination, and whether it becomes available to the website, the shop floor or both depends on where it physically ended up.
Where online selling looks different by business type
- D2C Brand Software, where the website is the main channel and everything on this page is the core operation rather than an addition.
- Apparel Retail Software, where variants, size guidance and high return rates dominate the online operation.
- Furniture Retail Software, where shipping is a delivery, the item is bulky and returns are collections rather than parcels.
- Beauty Retail Software, where batch and condition affect whether a returned item can go back into stock at all.
- Specialty Retail Software, where a small store reaches a wide audience and content quality carries the sale.
- Grocery Store Software, where online orders are picked from the same shelves and substitution rules matter more than shipping.
Why retailers choose Pentoggle for e-commerce management
Online orders in the same queue
One process for picking, packing and status across every order the business fulfils.
Content held with the product
Descriptions, attributes and images beside the item record, with the gaps listed so they can be fixed.
Picking confirmed by scan
The variant checked rather than read, which helps with the size and colour errors that reach customers.
Returns as a stock workflow
Matched to the order, inspected, given a destination according to condition, with the refund recorded against it.
Sits around your accounting, your POS and your web platform
QuickBooks, Tally, Xero and comparable systems continue handling the books. Your POS serves the counter and your web platform runs the storefront. Pentoggle runs the operation between them.
A useful number for e-commerce
The share of orders shipped complete and on time, read alongside the online return rate.
The first is the promise being kept. Complete matters as much as on time, because a partial shipment is a failure the customer experiences even when the parcel arrives promptly.
The second measures what happened after. A high return rate concentrated in particular items can point at content or sizing issues, among other possible causes such as product quality, fit, shipping damage or customer expectations.
Read both by item and by picker. Orders that ship late or incomplete often cluster on items that are hard to find or frequently out of stock, which may be a stock or location finding rather than a fulfilment one.
Ready to build retail e-commerce management software?
You know how many online orders you took last week.
You may not be able to say how many shipped complete, how many shipped late, or how many came back and are still in a box in the back room.
Describe your online channel, how you pick and ship and what comes back to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.