Organise product information

Prepare a reliable record for each product: name, description, photograph, price, variants and availability. If an item comes in different sizes or colours, define how each option is identified operationally. An attractive catalogue creates problems if customers can order a variant the team cannot locate or replenish.

Agree who will maintain the information. If an inventory tool already exists, assess whether it should be the primary catalogue source. Maintaining two manual lists tends to create differences between the website and operations. Integration requirements depend on the platform and should be tested with actual examples.

Define delivery conditions

Separate destinations you can reliably serve and identify conditions that differ between them. Local island delivery, inter-island shipping and orders outside the archipelago may need different rules. Customers need to understand costs and restrictions before committing to a purchase. Configuration should reflect the agreement with your logistics provider.

Include store collection if it is available, with clear instructions. Tax, customs and consumer information requirements depend on the specific operation. Validate those conditions with the relevant professionals before publishing them as final. Do not copy a mainland delivery policy and assume it fits every Canary Islands order.

Connect payment and order

Choosing a payment provider is only one part of the work. Check what happens when payment succeeds, fails or remains pending, and how the order management system interprets each state. Review confirmation emails and the information received by the team preparing the parcel. A success screen should not mark an unconfirmed transaction as paid.

  • A normal purchase and a mobile purchase.
  • Unavailable products and combinations of variants.
  • Accepted destinations, excluded destinations and collection.
  • Failed payment, cancellation and order confirmation.

Prepare daily operations

Before launch, assign responsibility for issues, returns, customer service and stock updates. Provide a simple procedure for recurring tasks. The interface should make buying easier, while the system and team must be able to fulfil the promise afterwards. Test handover rather than assuming that a finished page means a finished operation.

In an Odoo-connected project such as Kido Essence, catalogue work, platform configuration and the customer experience belong to the same discussion. A design demo is therefore different from an operational test. Recording what has been configured and what has been verified makes the launch decision more informed.

Further reading

Apply it to your business

Tell us what you need to improve. We’ll assess the scope with you.