EDGE omnichannel retail: reconcile store and online data

An EDGE omnichannel retail project should begin with the records that disagree today, not with a software demonstration. A retailer needs to identify how products, stock, orders, returns and customer transactions move between stores and online channels, then decide which system will become the reliable record. The current activity supports software costs for a defined solution, but the commercial benefit depends on clean data, ownership and daily operating discipline.

Map the current transaction path

Follow one product from purchase order to warehouse receipt, store transfer, online sale, return and refund. Note each system, spreadsheet and manual handoff. Count how often staff re-enter a code, price, quantity or customer detail. This reveals where an omnichannel tool may remove work and where a poor process would simply be copied into new software.

Use a four-week sample that includes promotions and returns. Record overselling, stock adjustments, cancelled orders, delayed fulfilment and reconciliation time. Separate data errors from supply problems. The project owner should be able to state which problem the proposed solution addresses and which problems remain outside scope.

Match the package to the official activity

The current omnichannel retail activity page describes a single-function solution for managing sales and inventories across online and physical channels. It states a S$15,000 activity cost cap, software support for up to 12 months and an 18-month completion period. Those published limits are not a substitute for the Letter of Offer, which controls an approved project.

Build the package in the SMEs Go Digital platform and reconcile it line by line to the vendor quotation. Licences, professional services, implementation dates and user counts should match. Maintenance and GST are listed as non-supported costs. Keep company-funded items visible so the board sees the full project cost rather than only the amount presented for grant support.

Choose the master data owner

Assign one person to approve product codes, units of measure, prices, tax treatment, locations and channel mappings. Duplicate stock keeping units and informal product names create false inventory differences. Clean these records before migration and retain the mapping from old values to new ones. The vendor can help load data, but the retailer must decide what is correct.

Write rules for new products, bundles, promotions and returns. Decide who may override stock, when a manual adjustment is allowed and how it is reviewed. A system can show a single quantity while staff continue to keep private spreadsheets. The operating policy must make the system record authoritative after an agreed cutover date.

Create a measurable one-year benefit case

The application asks for projected cost savings for one year after completion. Start with paid hours spent reconciling channels, correcting orders and preparing stock reports. Add avoidable courier costs, refunds or write-offs only when records support them. Do not call an expected sales increase a cost saving. Keep revenue opportunities in a separate, labelled estimate.

For example, if two employees each spend six hours a week reconciling stock at an attributable hourly employment cost of S$28, the annual labour baseline is about S$17,472 before leave and peak-season adjustments. Estimate the time after implementation, state the adoption assumption and retain the calculation. It is an internal planning example, not a promised government outcome.

Prepare acceptance and claim evidence

Set tests for store sales, online orders, stock transfers, refunds, promotions and end-of-day reconciliation. Include failure handling, user access and the first month-end close. The activity page requires a photo showing the deployed software and its unique identifier. Record the licence number, user account or other accepted identifier during deployment, not when the claim deadline is near.

Reconcile the approved package, invoice, payment, deployed identifier and acceptance record. The EDGE FAQ confirms that digital support counts within the S$30,000 sub-cap and the overall S$100,000 annual cap. Link the final file to the digital identifier claim guide and the annual cap register.

Decide whether the project is ready

Proceed only if the retailer has a named process owner, a clean product and location list, a quotation that matches the package, and enough staff time for testing and training. A one-week published processing estimate does not reduce the work needed inside the company. Do not make a payment, deposit or allow work to start before application submission.

If the main problem is warehouse design, channel strategy or a multi-system integration, this single-function activity may be too narrow. Compare it with other activities before using the UEN’s application opportunity. The business support cornerstone provides the broader route comparison.

Run a controlled cutover

Choose a cutover period that includes enough trading activity to expose errors but avoids the retailer’s highest-risk sales event. Freeze product and location changes shortly before migration, extract the agreed data set and record the row counts. Reconcile opening stock by location and investigate differences before transactions begin. A signed opening balance is more useful than a clean-looking dashboard whose starting quantities cannot be explained.

During parallel operation, define which system staff must use for each transaction. If both old and new systems can change stock, record the permitted reason and the person who will reconcile it. Test offline sales, cancelled payments, split fulfilment, partial returns, gift cards and exchanges. These cases often reveal whether the integration updates inventory once, twice or not at all.

After launch, review daily exception reports for at least one complete stock cycle. Compare system stock with a targeted physical count for fast-moving, high-value and frequently returned products. Record the cause of each adjustment and whether it requires data correction, staff training or vendor work. Acceptance should depend on the agreed error tolerance and resolution time, not simply on the date the software went live.

Management should approve the cutover result, unresolved exceptions and the owner of the remaining work. Keep the approval beside the baseline and the final benefit calculation. This gives finance a defensible link between implementation, operational change and the savings later reported in the claim file.

A useful omnichannel application explains exactly which records will become reliable, how staff will operate the new process and how savings will be measured. Set those decisions before choosing the package, then keep the approval, deployment and claim evidence in one traceable file.