Start with the stock decision, not the feature list

The most useful first question is not how many features a product has. It is which stock decisions your team struggles to make today. A buyer might need to know where units are available. A store manager might need to request stock. A warehouse team might need to understand which location is expecting a shipment. These are different questions, even when they use the same product record.

Write down three real examples from your operation before booking a software demonstration. Include the person doing the work, the information they need and the point at which the current process breaks down. This gives the conversation a practical starting point and makes competing demonstrations easier to compare.

Agree on what each quantity means

A total stock number can hide important differences. Ask how the proposed system defines on-hand, available, reserved and in-transit stock. Do not assume every system supports the same states or updates them at the same point in a workflow.

Use a simple example: ten units are on hand, two are reserved and four are moving to another location. Ask the demonstrator to show what each team sees before dispatch, during transit and after receipt. Record the agreed behavior rather than relying on a general promise of accurate stock.

Follow one product through your operation

Bring a representative product with the variations your team actually handles. For apparel, that may include a style, colour and size. Follow it through the proposed receiving, lookup, movement and counting process. Note where people need to enter information twice or switch systems.

Ask to see an exception as well as the ideal path. A short shipment, a missed scan or a transfer received in parts often reveals more about a workflow than a perfect transaction. Confirm which exceptions the proposed solution handles and which remain manual.

Treat migration as a separate workstream

Prepare a small, anonymized sample of your existing product and location data. Review identifiers, duplicate styles, units of measure and opening balances. Decide who owns cleanup and how the imported result will be checked.

A migration plan should explain the cutover point, validation responsibilities and what happens when something does not reconcile. Do not treat a general ability to import a file as a promise that your present data will transfer without preparation.

Compare the whole proposed scope

Ask for a written summary of the modules, locations, users, integrations and implementation tasks in each proposal. Include training, support arrangements, rollout sequence and any dependencies on hardware or external services. Compare the same scope rather than a headline subscription number.

For a RetailCore conversation, share your location count, existing systems and the three workflows you want to improve. The next useful step is a focused walkthrough and an agreed scope, not an assumption that every advertised module fits every operation.

This is an evaluation guide, not a specification of every RetailCore capability. Product availability and implementation scope must be confirmed separately.