Create Products in Magento 2 - Adobe Commerce

Creating a product in Magento 2, now part of Adobe Commerce, takes a few minutes through a guided form, but the quality of that record decides whether the product is found, priced correctly, taxed properly and sold. Only a name, a SKU and a price are mandatory. Everything else determines how well the catalog sells.

Think of the Monday meeting of an online retailer's commercial committee. The head of ecommerce reports that a new line of products went live on Friday, yet sales are close to zero. The category manager insists the products are the right ones. The finance controller has noticed that two items are being sold with the wrong tax treatment. Customer service reports that a customer was able to buy a product that was supposed to be hidden. Nobody made a dramatic mistake. Several people created products quickly, each leaving default values that nobody reviewed, and the catalog now behaves in ways nobody intended.

That is the executive reading of an apparently technical task. Magento 2 includes an intuitive product manager that lets store administrators configure and publish new products in minutes. Through a guided interface and preset attribute sets, the team can create simple, configurable, virtual or downloadable products with a few clicks, completing key fields such as name, SKU, price, tax class and visibility. This streamlined workflow reduces manual effort, minimizes errors and allows the team to keep the catalog up to date and aligned with the commercial strategy without advanced technical knowledge. The speed is a strength only when the company has decided, beforehand, what a correct product record looks like.

>> Geolocation in the Magento Checkout <<

How do you create a product in Magento 2?

The creation of a product starts with the button that opens the new product form. This walk-through uses only the basic attributes required for a product to be visible, added to the cart and sold in the store, and the same principle applies to the way Magento is extended through its interfaces when a company needs to create products at scale.

Button to create new products

Adobe's documentation for the simple product confirms that three fields are required, product name, SKU and price, and that the form is organized around an attribute set, which acts as the template for the product. A practical habit follows from this: create the product as disabled while information is being completed, and enable it only when it is ready to be published. The retailer in our opening scene would have avoided its Friday problem with that single rule.

Which attributes are required, and what do they mean for the business?

The product name is the name shown to customers in the store, used in searches and listings, and also the name used in the back office by administrators. It is therefore a commercial asset and an operating label at the same time, and it should follow a convention that the entire team understands. Baymard Institute's research on product lists found that missing key information in listings makes shoppers guess or click through each page, and that 35% of the sites in its benchmark did not provide the five essential attributes, including price and a clear title. A name that carries the right information is the first defense against that loss.

The SKU is the unique identifier of the product. If the company has an inventory system, an ERP or an already assigned code, the recommendation is to use it, or a consecutive number if necessary, and if the product has a barcode it is a very good option to become the identifier. The decision matters beyond the catalog, because the SKU is what connects the store with inventory, billing, logistics and reporting. A company that creates its own codes in the ecommerce system, separate from the ERP, is building a reconciliation problem for the future.

The price is the base price used to calculate sale prices, and it is the field where most of the commercial logic converges. This price is affected by other configurations in the store such as promotions, taxes and discounts. When a product is created it is assigned a tax class, and that class changes the price of the product if its percentage is greater than zero. In Magento it is also possible to add a fixed value to the final price. Catalog discounts apply to the catalog, cart discounts are applied through coupons or automatically to the cart, special prices are assigned for periods of time, and a customer group price is designated for specific groups. Adobe's reference of product data attributes describes special price as the discounted price during a specified date range, and group and tier prices as discounts for customer groups or quantities. The practical consequence is that the final price a customer sees is the result of up to six layers, and nobody should assume that the base price is the price paid. Our article on how to create a catalog price rule in Adobe Commerce shows how one of those layers is built.

The last required element in the author's list is the enable switch, which indicates whether a product is available in Magento. It is the simplest control of publication, and in a well-run store it is the last step of a review, not the first.

>> Uploading Products to Adobe Commerce <<

Why should the attributes that are not required be reviewed?

Some attributes already come with a default value, and they must nevertheless be validated and adjusted, if necessary, so that they align with the commercial, operational and regulatory needs of the store. Leaving them with the original configuration can lead to inconsistencies in how products are displayed, priced, taxed or indexed in search, and it can affect both conversion and catalog management. These attributes are filled in automatically with a predetermined value taken from a predefined list, which Magento uses as a starting point. Before publishing, it is advisable to verify each value and confirm that it is appropriate for the product type, the sales channel and the customer segment the store is targeting.

The tax class is always assigned when a product is created, and it can be None, which applies a 0% tax. That default is convenient for testing and dangerous in production. Adobe's documentation lists the options available, including taxable goods and, depending on configuration, VAT classes, so the choice should be made by someone who understands the tax obligations of each market. In the retailer's committee, the two products with the wrong tax treatment came from here, and the correction involves finance and, potentially, customers.

Visibility determines whether the product can be seen on the storefront, and it has four values. According to Adobe's reference, the options are Not Visible Individually, Catalog, Search, and Catalog, Search. A product set to Catalog is visible when browsing categories but not through search. A product set to Search appears in search results but not in category listings. A product set to Catalog, Search appears in both and is the usual choice for a product that should be fully available. Not Visible Individually deserves a note. The author describes it as a state in which the product does not appear in catalog or search but can still be seen and bought by someone who has the link. Adobe describes it as the setting for a product that appears only as a variation of another product, such as the simple products inside a configurable product, and a direct page should not be expected. The setting is therefore appropriate for components, and it is not a reliable way to hide a product from the public.

The URL key is created by default from the product name when the product is created, although a specific value can be entered. It is a small field with a long life, since the URL of a product is shared, indexed and linked for years. Google's guidance on URL structure recommends readable words instead of long ID numbers and hyphens to separate words, and Adobe notes that a change of URL key can be accompanied by a permanent redirect from the old address. A good URL key policy spares the company from managing redirects later.

>> Content personalization in Magento Commerce <<

What does the SEO information add to a product?

The form also asks for information related to search engine optimization. It is not mandatory, but it is essential for the products to appear in the first search results. Meta title, meta description and a clear URL key allow a search engine to understand what the product is, and give the shopper a reason to click on the listing instead of a competitor's. In stores with thousands of products, the efficient approach is to define templates for these fields and adjust them manually for the products that matter most for revenue.

Once these steps are completed, the product has been created. With a few clicks and very little information, it is possible to publish a product that is available to the public, accessible by URL, found in product search and displayed in product listings. The author recommends reviewing the other non-required attributes of Magento as well, since they give completeness to the store and offer a better experience to the users who browse it.

Which product type should a business choose?

The creation form offers simple, configurable, virtual and downloadable products, and the choice is a commercial decision before it is a technical one. A simple product is a single item with its own SKU and stock, and it is the right model for a product that has no options. A configurable product groups several simple products that differ in an option such as size or color, so that the customer chooses a variation on one page. A virtual product has no physical delivery, as with a service or a subscription, and a downloadable product is a digital file the customer receives after the purchase.

Each type changes what the business must manage. Configurable products simplify the shopper's decision and concentrate reviews and search relevance on one page, but they multiply the SKUs that inventory and reporting must follow. Virtual and downloadable products remove shipping from the equation and bring other questions, such as how access is granted and how returns are handled. An executive does not need to configure them, yet should ask which model the team is using for each product family and why, because the answer shows whether the catalog was designed or simply accumulated.

What are the trade-offs and risks of fast product creation?

The principal risk is inconsistency at scale. Each person who creates a product makes small choices, and without a convention the catalog becomes a collection of personal styles. Names differ in format, tax classes are chosen by guess and visibility is used as a hiding place. The effect on customers is confusion and on the company is reporting that cannot be trusted. The second risk is price complexity. The six layers of price that Magento allows make it possible to run a sophisticated pricing strategy, and also to create contradictions, such as a special price that conflicts with a cart rule. The third is dependence on individuals. When only one person knows why a catalog is organized as it is, the company has a continuity risk.

The countermeasure is not heavy bureaucracy. It is a one-page standard that states the naming convention, the SKU source, the allowed tax classes by market, the visibility policy and the person who approves new products. Such a standard can be applied in minutes and prevents most of the incidents described above.

What does this mean for the C-level?

For the chief executive and the head of ecommerce, the catalog is the shop window, and its quality is a growth lever. Products that are named clearly, categorized properly and visible through the right paths convert better, and the cost of correcting them later is higher than the cost of creating them well. The question to ask the team is how long it takes from the decision to launch a product to the moment it can be bought correctly, and how many corrections follow.

For the chief financial officer, the focus is margin and compliance. Price layers, tax classes and special prices decide how much the company earns on each sale and whether it complies with tax rules. A review of the products with the highest revenue, looking at their effective price and tax treatment, is a simple and inexpensive control. For operations and technology leaders, the opportunity is efficiency: a SKU shared with the ERP, templates for common fields and a bulk upload process for large catalogs reduce manual work and errors. For marketing, the attributes and SEO fields are the raw material of discoverability.

How should a director start next week?

Pick the twenty products that generate the most revenue and open their records with the person who created them. Check the name, SKU, base price and the layers that modify it, the tax class, the visibility and the URL key. Ask whether each choice was deliberate. In most stores this half hour reveals at least a few defaults that nobody had reviewed, and it gives the committee a concrete sense of the size of the issue.

With that evidence, write the one-page standard, name an owner for new products and agree that every new product is created disabled and enabled only after a second person has looked at it. For large catalogs, move to a bulk upload process with the same checks. Revisit the standard after a month, adding what the team learned, and measure the share of products that go live without later corrections. A small discipline like this rarely makes headlines, yet it protects revenue every day.

How ICX helps

ICX Consulting treats the catalog as a commercial asset. Our digital ecommerce for B2C and B2B practices define catalog governance, pricing layers and the processes that keep product data accurate, and our pricing and revenue team ensures that the price a customer pays reflects the strategy of the business. Where Adobe Commerce is the platform, we implement it and integrate it with your ERP and inventory systems so that products are created once and correctly.

To structure categories, attributes and navigation before loading products, use the Information Architecture Toolkit. Is your catalog helping or hurting your sales? Request a diagnostic with an ICX consultant.

Frequently asked questions

Which fields are mandatory when creating a product in Magento 2?

Product name, SKU and price are the required fields of a simple product, according to Adobe. Other attributes carry default values, such as tax class and visibility, that should still be reviewed because they affect pricing, taxes and discoverability even though the form does not force you to complete them.

What is the difference between Catalog and Search visibility?

Catalog makes the product visible when browsing categories, Search makes it appear in search results, and Catalog, Search does both. Not Visible Individually is meant for products that exist only as part of another product, such as the options of a configurable item.

Should the SKU come from the ERP?

Whenever the company has an ERP or inventory system, yes. A single code across systems avoids reconciliation work and errors in stock and billing. If a product has a barcode, it is also a sound basis for the identifier.

Why does the final price differ from the base price?

Because taxes, fixed increases, catalog discounts, cart discounts, special prices and customer group prices can all modify it. Review the layers that apply to a product before publishing it, and document who owns each of them.

A store that creates products with the same care it gives to its brand builds a catalog that sells every day, without asking for attention. If your team wants to review its product data standards and pricing layers, we would be pleased to explore it with you.