The website itself and the marketplace can play different roles in sales. The marketplace provides a transaction environment with platform rules, while the website provides space to organize information, brand experiences, and service flows according to business needs. The choice needs to follow how customers buy, the team's ability to manage orders, and overall costs. Having both channels is not necessarily beneficial if the operational work is not ready.
For certain businesses, the website is sufficient as a center for information and requests for offers, while standard product transactions continue to take place in the marketplace. Other businesses require direct transactions on the website. FourVM places the division of channel roles before discussing features, so that development does not start from the desire to have an online store without clear operational goals.
Starting from the customer purchasing journey
Write down how buyers find products, compare options, ask questions, pay, and receive goods. Products with standard sizes may be easy to purchase through catalogues. Products that require consultation, customization, or specific purchase quantities may require a conversation before a final price is set.
Also check out the unanswered questions in the channel now. Does the customer need an explanation of ingredients, how to choose, instructions for use, or technical documents? This need can be a reason to build an information website without directly adding a basket and payment system.
Don't equate the presence of visitors with readiness to buy. Many visits may come from people who are just learning about the product. Determine the appropriate actions on each page, then link them to a follow-up process that the team is actually capable of carrying out.
Determine the specific function of each channel
Create a division that can be explained in one sentence. For example, a marketplace for ready-to-ship goods transactions and a website for product guides and corporate purchasing offers. The division prevents teams from publishing two different catalogs for no apparent reason.
For customers, prices, availability and terms of service need to be explained consistently. If there are differences between channels, write down the context and check for compliance with applicable platform rules. Don't design transaction movements assuming all platforms allow the same patterns.
Marketplace terms and fees are subject to change. Read the official rules of the platform you are actually using before making a decision. This article does not specify rates, data usage rights, or transaction policies for specific marketplaces as each has different terms.
Calculate costs at the order level
Compare the costs incurred in obtaining and serving orders, not just the costs of creating a website. On each channel, note applicable components such as promotions, payments, platform services, packaging, customer service, returns, and team time. Avoid calculating one component twice.
Use simulation to understand the formula. If the order value is IDR 300 thousand, goods costs IDR 180 thousand, promotions IDR 25 thousand, transaction and service fees IDR 15 thousand, and fulfillment IDR 20 thousand, the remaining contribution is IDR 60 thousand. This figure is an illustration, not a benchmark for margins or marketplace rates.
Websites also have operational costs that need to be allocated, such as domains, hosting, maintenance and content management. If the simulated monthly fixed costs are IDR 1.2 million divided by 60 orders, the allocation is IDR 20 thousand per order. If the order changes, the allocation changes accordingly; Don't conclude that the website must be cheaper.
Prepare a product and inventory reference
Two channels add to the upgrade work. Determine product code references, variants, descriptions, photos, prices and stock used by the team. If there is no integration, write down the manual process and who updates the data after an order is received.
Starting from the number of products that can be treated. A small catalog with correct information is easier to account for than an entire product published but rarely checked. Note the update time so the team knows whether the data is still suitable for receiving orders.
Google's guide to product data explains the use of structured data and Merchant Center to help search engines understand product information. Neither guarantees any particular sales or appearance. The basis that needs to be prepared remains product data that is accurate and consistent with the page the buyer sees.
Design the experience after the customer acts
If the website is used to request a quote, explain the data needed and who is following up. If you provide payments, check order chaining, confirmations, failure handling, and matching orders to payments. Each additional function brings work after the page has been created.
The W3C Forms Tutorial can be a reference for labels and instructions that help users complete forms. Apply it to the information needs that are needed. Long forms for no reason can add work to customers and generate data that the team doesn't use.
Describe service channels for post-purchase questions. Customers coming from two places still need consistent answers. Establish a way to record complaints or order changes so that the conversation isn't lost when the clerk changes or the customer calls another channel.
Simulation case study: a product brand with a limited catalogue
This simulation is not a FourVM customer report. A brand has twelve products and manages orders through a marketplace. The team wanted to create a website because questions about ingredients and how to choose products kept recurring, but did not yet have additional staff to manage new transactions.
They start from an information website that contains guides, specifications, and purchasing channels that comply with the platform's provisions. Product data is checked from a reference list. Website baskets are on hold until payment, stock and customer service responsibilities can be determined.
The lesson is that websites can provide different functions without having to directly copy the entire marketplace process. The initial evaluation is directed at whether the information helps answer the buyer's questions. Increased sales are not stated to be a definite result of the addition of the website.
Simulation case study: suppliers for corporate purchasing
A supplier sells standard goods at retail, but also accepts bulk purchase requests. Prospective corporate customers often require specification documents and quotations that match quantities. The unit purchase flow does not adequately explain these needs.
The team divided roles: the existing transaction channel continued to handle standard items, while the website provided technical information and forms for corporate needs. They designate the recipient of the request, a list of supporting documents, as well as how to record the offer. Specific prices are discussed after the need is clear, not guessed by the system.
The lesson is that website functions need to follow a different sales process. Adding payment methods does not necessarily solve corporate purchasing needs. What is more important is the completeness of the information, the line of inquiry, and the team's readiness to provide actionable answers.
Measure results without adding up arbitrary data
Determine the size that suits the function of the channel. Information websites can be assessed through the use of relevant guides or queries. Transaction websites can examine the journey from viewing the product to purchase and return. Transaction figures still need to be matched with business order records.
GA4 documentation describes e-commerce events to measure actions such as viewing products, adding to cart, and purchasing. Events require implementation as well as inspection; the existence of Analytics does not prove that all actions have been recorded. Moving to another channel may also limit the visible data link.
Avoid aggregating users from multiple reports as if they were all different people. One customer can visit the website and then buy on the marketplace. Note these limitations when comparing costs and outcomes, so that decisions do not rely on misleading aggregate figures.
Frequently asked questions
Is it mandatory for websites to have online payments? No. First determine whether the customer needs a direct transaction, consultation, or offer. To organize page requirements, use guide to creating a company website as initial planning material.
When is it worth running both channels together? When each has a clear function and the team is able to maintain information and follow up on orders. In discussions with FourVM, these needs can be translated into development stages, starting from the functions that are most needed and most readily managed.
Source
- Google Search Central — Share your product data with Google. Structured data and product data . The date of publication is not recorded; accessed 14 November 2026.
- Google Analytics — Measure ecommerce. Events to measure shopping behavior . The date of publication is not recorded; accessed 14 November 2026.
- W3C WAI — Forms Tutorial. Labels and instructions on forms . Updated March 27, 2026; accessed 14 November 2026.