The online store is part of the company's daily work. Before building, you need to determine not only the look of the catalogue, but also the sources of data, state service and liability for orders.
Draw the path of one order
Choose an example product and describe what happens from its addition to the catalogue to the end of customer service. Who sets the price, updates availability, prepares the shipment and answers the status question? This description reveals needs that are not seen on the homepage project.
For a company operating stationary sales in Warsaw and online sales, it may be important to have a common source of information about the goods. This does not mean that each store needs extensive integration. It is important that the rules for updating data are known and feasible with the planned number of orders.
Identify the source of each information
Split product data, prices, stock stocks and order statuses. They can come from different systems, but for each type of data you need to specify an overriding system and the direction of exchange. Otherwise, a manual amendment in the store panel can be replaced with another import.
- When is availability refreshed?
- What's a client supposed to see during a break in connection?
- How will the team recognize an order requiring manual intervention?
- Does personal reception have separate rules for preparation?
- Where is the history of changes to the order proven?
Example: Last play in two channels
Imagine a product sold at the same time at a fixed point and on the Internet. The project should specify the moment of the art booking and the way in which the availability conflict is handled. The “available product” message itself does not solve this process. An employee procedure is also needed when the data cannot be confirmed immediately.
This is a scenario to check with the contractor and supplier of the storage system before the start of the sale, not only after the first non-compliance.
Run a range that you can handle
The first version may include the selected catalog, agreed deliveries and the most important processes. Subsequent integrations should be added after the basics have been arranged. Receipt of implementation should include back-up work as carefully as the purchase on the phone.
Read also how to determine the scope of the first store i how to test the store design on a real catalog.
