Create and Edit Products
Create and maintain products across core Product, Web, and Inventory sections without mixing operational, public, and stock data.
Updated
Overview
The product form separates product management into three main areas: Product, Web, and Inventory. Product contains core operational information. Web controls public website content and visibility. Inventory controls stock-related behavior where inventory tracking is used. A product should be reviewed across all applicable sections before it is considered complete.
When to use this
- Add a new product.
- Update an existing product.
- Maintain core product information.
- Configure product attributes, moldings, or packaging where applicable.
- Prepare a product for the public website.
- Maintain English and Turkish website content.
- Configure inventory tracking.
- Set box, lot, reorder, or low-stock-related information.
Product form structure
| Section | Purpose |
|---|---|
| Product | Core product identity and operational information. |
| Web | Public website visibility, multilingual content, and SEO-related information. |
| Inventory | Stock tracking, packaging/box behavior, lot information, reorder settings, and low-stock awareness. |
Recommended workflow
-
Create or open the product
Open Products and either create a new product or edit an existing one. -
Complete the Product section
Maintain core operational information and review structured information such as attributes, moldings, and packaging where applicable. -
Review packaging information
Verify package quantity and coverage values, especially for box-based quantities and inventory tracking. -
Open the Web section
If the product should appear publicly, review website visibility, English/Turkish content, slug, meta information, and public descriptive content. -
Review AI-generated content where used
Treat AI-generated product web content as a draft and verify facts, specifications, wording, and SEO relevance before publication. -
Open the Inventory section
If stock tracking is required, review inventory tracking, packaging/box information, lot information, reorder level, and low-stock behavior. -
Save the product
Save after reviewing all applicable sections. -
Verify public output when applicable
If the product is intended for the public website, review the published result rather than assuming saved admin values produce the intended page.
Example scenario
A company adds a new flooring product. It creates the core product record, verifies packaging because the product is sold by box, prepares the Web section and SEO fields, then configures inventory tracking and reorder information. After saving, the public page is reviewed.
Product data vs public web content
| Data type | Purpose |
|---|---|
| Product data | Operational/catalog use inside FBM. |
| Web content | Customer-facing public website content. |
| Inventory data | Stock and replenishment-related behavior. |
AI-generated content is a draft
FBM includes an AI Product Web Content Generator. Generated content should be reviewed for product accuracy, wording, specifications, and SEO relevance before publication.
Important notes
- Review Product, Web, and Inventory separately.
- Packaging values can affect inventory and quantity calculations.
- Public content should be reviewed before publication.
- AI-generated content is a starting point, not a substitute for product verification.
- Website content and operational product data serve different purposes.
- Use consistent structured attributes across similar products where possible.
Common mistakes
| Mistake | Why it matters | What to do |
|---|---|---|
| Completing only the Product section | Website or inventory configuration may remain incomplete. | Review all applicable tabs. |
| Using incorrect packaging values | Box and inventory calculations can become inaccurate. | Verify package quantity and coverage data. |
| Publishing AI content without review | Product facts or marketing language may be unsuitable. | Review and edit generated content. |
| Treating operational fields as complete SEO content | Public pages may remain weak or incomplete. | Maintain the Web section separately. |
| Enabling inventory without reviewing quantity/packaging | Stock indicators may become misleading. | Verify configuration before relying on inventory values. |
What happens next
- The product becomes available to applicable operational workflows.
- Website-visible products can use their configured public content.
- Inventory-enabled products can participate in stock tracking.
- Catalog, website, and inventory settings can continue to be maintained independently.