Catalogue and Product
We plan categories, filtering, photos and descriptions. We take into account variants, availability and information needed to choose from.
Offer / BXM Multimedia
Store creation Shopping simple from the first click.
We design online shops with a clear catalogue, convenient product card and orderly order handling. We combine customer experience with the daily work of the seller.
Let’s discuss your projectStore creationIdea → project → implementation
Customised to your company
What can we prepare?
Basket and order
We design the way to purchase: customer data, delivery and payment. We also check errors and discontinued transactions.
Panel and integration
We set orders and links to warehouses and other systems. The scope of integration is due to the way the company works.
Implementation and further cooperation
A store that can be run and developed.
Starting sales is the beginning of work on the catalogue, purchase and order handling. We design a store for people who will run it every day.
Sales model
Products, variants, payments and deliveries. We set a way to update the stocks and prices.
Order sample
We test purchases, messages, statuses and agreed integrations before publication.
Development of sales
We analyze places of resignation, develop descriptions of categories and plan changes based on customer behaviour.
Service Guide
Creating an online store: from catalog to order handling
The store is a sales process, not just a list of products with a basket. The project includes data, presentation of the offer, payment, delivery and work of the team after placing an order.
Catalogue of products and rules of sale
Before choosing the solution, we determine the number and types of products, variants, availability and way of updating prices. We determine whether you need kits, personalization, wholesale orders or different conditions for customer groups. These decisions affect the data structure and later management convenience.
Categories should correspond to the method of searching for the product, and filters help narrow down the choice. Not every attribute must be a filter. It is worth preparing a sample of the actual catalog in advance: descriptions, photographs, parameters and variants.
Expand Subject:
Product card and purchase on the phone
The buyer needs clear information about the variant, price, availability and delivery conditions. Photos should show details, and descriptions explain the application and limitations. Important information cannot be hidden in graphics only or require a mouse to raid.
The purchase process is tested on a small screen and using a keyboard. We check error messages, change the number of products, unavailable variant and return to cart. The form should ask for the data needed for implementation, rather than forcing unnecessary steps before buying.
Product description should help to compare variants: specify the dimensions, application, package content and restrictions relevant before purchase. Reproduction of the manufacturer's description on many similar cards does not replace information useful to its own customers. A link from the purchase guide should be directed to the right category, and from the product to matching accessories, if they really help in choosing.
Expand Subject:
Payments, delivery and company systems
The scope of integration is agreed on specific suppliers and their capabilities. It is necessary to determine where the stock comes from, when the product is booked and which system changes the status of the order. Synchronization of prices and stocks requires rules for handling delays and conflicts.
We test the payment successfully, discarded, interrupted and confirmed with delay. The re-notification should not create a second execution. Equally important are e-mail notifications, documents and order view for the employee. They decide whether the sale can be handled efficiently.
Expand Subject:
Visibility and development after launch
The SEO of the store includes descriptions of categories, available product pages, logical linkage and control of options of addresses. Filters can create many similar views, so we determine the indexing rules consciously. When migration takes a map of old addresses and how to deal with withdrawn products.
After the publication, we observe product search, adding to the cart and finishing the purchases. We combine requests with customer service questions. Further functions should solve a recognized problem, not increase the weight of the page without justification. We also check speed on product categories and tabs.
The change of the store platform also requires protection of the addresses of categories and products. We maintain useful addresses or prepare redirections to the corresponding pages. The temporarily unavailable product can continue to help the customer if the card provides availability and reasonable alternatives. Once the product has been permanently removed, the decision depends on whether there is a real replacement; redirecting each old card to the store's home page does not solve this problem.
Example: a product available in many variants
One model of the product can be in several sizes and colors, with different stock states. We determine what is a common description and what belongs to the variant: photo, price, code or availability. The buyer should clearly see which variant adds to the basket and whether it can be ordered.
The test includes a situation in which the selected combination ceases to be available before payment. The system should explain the problem and allow the change of choice. After purchase, the variant identifier must be placed on the order and further integration. Without this, the correct presentation in the store will not ensure proper preparation of the shipment.
Good start.
From Chatting
to a particular plan.
We set the goal, scope and way of receiving the work. We develop the project on the basis of agreed needs and materials.
See our realizationsWhat is worth preparing for the conversation?
- Examples of products and variants
- Methods of payment, delivery and order handling
- List of systems to connect to the store
You don't have to have the specifications in place, and we'll work out the most important decisions together.
Before the first conversation
It's worth knowing.
Can I move the catalogue from the current store?
We check the data format, photos, variants and product identifiers. The sample import allows to detect shortcomings before moving the entire directory.
Is the store gonna be comfortable on the phone?
The mobile view is part of the project. We check the selection of variants, filtering, forms and the transition from product to payment.
What does the valuation of the store depend on?
From the model of sales, catalogue, integration and scope of the project. For the conversation it is worth preparing examples of products and description of order execution.
Is the store's maintenance part of the implementation?
We describe the implementation and current care separately. Maintenance may include updates, monitoring integration and development of functions. Adding products and conducting campaigns require agreement on a separate scope.
Your next step
A store that can be run and developed.
Starting sales is the beginning of work on the catalogue, purchase and order handling. We design a store for people who will run it every day.
Let's start with your idea.
Write a few sentences about the project or call me.