> For the complete documentation index, see [llms.txt](https://docs.sellermagnet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sellermagnet.com/dashboard-and-analytics/dashboard-overview/products-management.md).
# Products Management
{% hint style="info" %}
**Difficulty:** ๐ก Intermediate ยท **Reading time:** \~10 min
{% endhint %}
{% hint style="success" icon="rocket" %}
**Open this page in your dashboard:** [**Go to Products Management โ**](https://dashboard.sellermagnet.com/dashboard/products)
{% endhint %}
The **Products Management** page is where you manage your entire product catalog, track Cost of Goods Sold (COGS) through the batch system, monitor stock levels, and configure inventory alerts. Accurate product data here is the foundation for every profit, margin, and ROI calculation throughout SellerMagnet.
> Every profit number you see on the Dashboard, Orders, and Reports pages depends on the COGS data entered here. If your profit figures look wrong, this is the first place to check.
{% hint style="warning" %}
**Critical First Step:** Before analysing any profit data, create product batches for your top 10 revenue-generating SKUs. This takes about 15 minutes and unlocks accurate profit calculations across the entire platform.
{% endhint %}
***
## ๐ฅ Video Walkthrough
{% hint style="info" %}
**Video tutorial coming soon.** A full guided walkthrough of this feature will be available here shortly.
{% endhint %}
***
## ๐๏ธ Page Structure
| Section | Purpose |
| ------------------------- | ---------------------------------------------------------------------------------- |
| **Products Table** | Full catalog with search, sort, and pagination |
| **Product Batches Modal** | COGS management, batch creation/editing, and stock tracking |
| **Stock Forecast** | Projected stockout dates, daily usage, and reorder timing |
| **Inventory Alert Rules** | Configurable thresholds for out-of-stock, low inventory, and restock notifications |
***
## Products Table
The main products table lists every product in your connected Amazon catalog.
### Table Columns
| Column | Description | Sortable |
| --------------- | ------------------------------------------------------------------------------------------------ | -------- |
| **Product** | Product image, title, ASIN (Amazon Standard Identification Number), and SKU (Stock Keeping Unit) | Yes |
| **Marketplace** | Amazon marketplace where the product is listed | Yes |
| **Fulfillment** | FBA or FBM indicator | Yes |
| **Stock** | Current available stock quantity | Yes |
| **Price** | Current listing price | Yes |
| **COGS** | Cost of Goods Sold per unit (from batch data) | Yes |
| **Units Sold** | Total units sold in the selected period | Yes |
| **Revenue** | Total revenue generated | Yes |
| **Profit** | Net profit after all costs | Yes |
| **Margin %** | Profit margin percentage | Yes |
| **ROI %** | Return on investment percentage | Yes |
| **Actions** | Batch management and other quick actions | No |
### Search and Filtering
* **Search bar:** Filter by product name, ASIN, or SKU
* **Marketplace filter:** Select a specific marketplace or view all
* **Only active products:** A toggle to hide inactive/closed listings
* **Fulfillment filter:** Click the funnel icon in the toolbar to filter by **FBA Only** or **FBM Only** (use **Clear All** to reset). An active filter shows a small badge on the funnel.
* **Pagination:** Navigate through your product catalog with configurable page sizes
{% hint style="warning" %}
Products with no batch data will show COGS as EUR 0.00, which means profit calculations are overstated. Look for products with suspiciously high margins, they likely need batch data.
{% endhint %}
### Group by Parent ASIN (Variant Grouping)
Products that share a parent ASIN (sizes, colours, and other variations) can be rolled up into a single parent row. Use the **Variants** button (layer-group icon) in the toolbar to toggle grouping:
* **Default view** lists every child SKU on its own row.
* **Grouped view** (button highlighted, icon switches to the grouped state) collapses child SKUs under their **parent ASIN** so you can read catalog performance at the variation-family level.
Your choice is remembered - the toggle state persists across page reloads.
***
## Product Batches (COGS Management)
The batch system is SellerMagnet's approach to tracking the Cost of Goods Sold for your products. Each "batch" represents a purchase of inventory at a specific price.
### Why Batches Matter
| Without Batches | With Batches |
| ------------------------------------------------ | -------------------------------------------- |
| Profit shows as "Revenue minus Amazon Fees" only | Profit accurately reflects true COGS |
| Margin appears artificially high | Margin reflects actual profitability |
| ROI calculation is meaningless | ROI shows true return on your investment |
| Stock forecasting unavailable | Stock depletion and reorder timing available |
| Cannot track purchase price changes over time | Full history of procurement costs |
### Opening the Batches Modal
1. Navigate to **Dashboard > Products**
2. Find the product you want to manage
3. Click the **batch/edit icon** in the Actions column
4. The Product Batches modal opens
### Batch Modal Layout
The modal is organized into these sections:
| Section | Description |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Product Header** | Product image, name, SKU, total units sold |
| **Batch List** | Scrollable list of all existing batches for this product |
| **Batch Form** | Create or edit a batch with fields for quantity, per-unit costs (net, tax, shipping, payment fee, customs, additional), arrival date, and currency |
| **Stock Forecast** | Visual chart and KPIs projecting inventory depletion |
***
## Easy Mode: Flat Cost per Unit
At the top of the batch modal is an **"Easy mode: flat cost per unit"** toggle. Turn it **on** to skip inventory batches entirely and enter a **single flat cost per unit** that is used for **all** profit, margin, and ROI calculations for that SKU.
* **Turning it ON** hides the batch fields and shows one **Cost per unit** input plus a currency selector. While active, this flat cost **overrides any batches** for that SKU.
* **Turning it OFF** (or clicking **New Batch** / an existing batch) returns you to full batch management.
In the products table, a **"Easy mode"** badge marks any SKU using a flat cost, and the flat value appears in the **COGS** column.
### Flat Cost vs. Batches - Which Should I Use?
| Use **flat cost** (Easy mode) | Use **batches** |
| ------------------------------------------------------ | ---------------------------------------------------- |
| Simplest option - one cost per unit, no stock tracking | Track cost per purchase lot and FIFO allocation |
| Your buy price rarely changes | Your buy price changes between reorders |
| You do not need stock forecasting | You want stock forecasting and returns-back-to-stock |
{% hint style="info" %}
Start with **Easy mode** if you just want correct profit numbers fast. Switch to **batches** later when you need FIFO cost tracking or stock forecasting - no data is lost, the toggle simply changes which cost source is active.
{% endhint %}
### Bulk: Flat Cost for Multiple Products
You do not have to open the batch modal one SKU at a time. Select several products with the row **checkboxes** in the table, then use the bulk actions that appear in the toolbar to set a flat cost on all of them at once.
1. Tick the **checkbox** on each product row you want (or the header checkbox to select the whole page). The **bulk action buttons** appear in the toolbar.
2. Click **Bulk add batch**. The bulk modal opens.
3. Turn on the **"Easy mode: flat cost for all selected"** toggle at the top of the modal.
4. Enter a single **Cost per unit** and pick the **currency**.
5. Click **Apply flat cost**. The same flat per-unit cost is written to every selected SKU and immediately overrides their batches for COGS.
{% hint style="info" %}
The same bulk modal also lets you create a full **inventory batch** across all selected products (name, units, and the per-unit cost breakdown) when you leave Easy mode off - handy when you received the same lot across several SKUs.
{% endhint %}
***
## ๐ฃ Step-by-Step: Creating a New Batch
1. Open the **Product Batches modal** for your product.
2. Click the **"New Batch"** button in the modal sidebar.
3. Fill in the batch form. Fields marked **\*** are required; every cost field is **per unit** and combines into the batch's landed COGS:
| Field | Description | Example |
| ------------------------ | ------------------------------------------------ | ----------------- |
| **Batch Name \*** | A descriptive label for this purchase lot | "Q2 Main Reorder" |
| **Total Units \*** | Number of units purchased | 500 |
| **Unit Net Cost \*** | Net purchase price per unit (ex-tax) | EUR 4.75 |
| **Unit Tax Cost** | Tax per unit (VAT, sales tax) | EUR 0.90 |
| **Unit Shipping Cost** | Inbound/freight shipping allocated per unit | EUR 0.35 |
| **Unit Payment Fee** | Payment-processing fee per unit (if applicable) | EUR 0.10 |
| **Unit Customs Cost** | Import duties / customs per unit | EUR 0.20 |
| **Unit Additional Cost** | Any other per-unit cost (inspection, prep, etc.) | EUR 0.15 |
| **Arrival Date** | Date the inventory was received | 2026-03-15 |
| **Currency** | Currency of the purchase prices | EUR |
> **Batch names** are unique within a product and are how you tell purchase lots apart (e.g. "Q2 Main Reorder" vs. "Q3 Restock"). Reusing an existing name for the same SKU updates that lot rather than creating a second one.
4. *(Optional)* Tick **"Apply these costs to past unlinked orders"** - see below.
5. Click **"Create"** to save the batch.
6. The batch appears in the list, and COGS calculations update across all dashboards.
{% hint style="success" icon="rocket" %}
**Pro Tip:** Create a new batch every time your purchase price changes, even if it is from the same supplier. This maintains an accurate historical record of COGS and lets you see how procurement cost changes affect your margins over time.
{% endhint %}
### Applying a Batch to Past Orders
By default a new batch only covers orders going forward (via FIFO). If you are entering a batch for inventory you have **already been selling**, tick **"Apply these costs to past unlinked orders"** in the create form. SellerMagnet then:
* Applies the batch's per-unit costs to **every past order item that does not yet have a batch attached**, and
* **Auto-expands the batch capacity** so it covers all those linked past orders.
A confirmation dialog ("Apply costs to historical orders?") spells out the scope and warns that it **recomputes historical Profit, Margin, and ROI** for that SKU.
{% hint style="info" %}
This action is **reversible**: deleting the batch from the Manage Batches modal undoes the historical changes. It is the fastest way to back-fill COGS for a SKU you started selling before you began tracking batches.
{% endhint %}
### Returns Back to Stock
The batch modal header has an **"Add returns back"** toggle. When **on**, units that customers return are added back to this product's **sellable** stock count (so your stock forecast and units-remaining figures reflect re-sellable returns). Leave it off if returns are not resold. The account-wide default for this is set in **Settings > General โ Default returns sellable**.
### Editing a Batch
1. Click the **edit button** on an existing batch in the list.
2. Modify any field (quantity, price, date, notes).
3. Click **"Edit"** to save changes.
4. All profit calculations that reference this batch update automatically.
### Deleting a Batch
1. Click the **delete button** on the batch you want to remove.
2. A confirmation dialog appears: *"Are you sure you want to delete this batch?"*
3. Click **"Delete"** to confirm.
{% hint style="danger" %}
Deleting a batch removes its COGS data from all historical profit calculations. Only delete batches that were entered in error. If you need to correct a batch, use the Edit function instead.
{% endhint %}
***
## Stock Forecast
The Stock Forecast feature is integrated into the Product Batches modal and provides predictive analytics for inventory management.
### Forecast KPIs
| KPI | Description | Health Indicator |
| ------------------ | ----------------------------------------------- | ---------------------------------------------------------- |
| **Current Stock** | Units currently available in Amazon's warehouse | Cyan icon |
| **Days Remaining** | Estimated days until complete stockout | Yellow icon; shows "Healthy" / "Warning" / "Critical" pill |
| **Daily Usage** | Average units sold per day (30-day lookback) | Green icon |
| **Stockout Date** | Projected date when inventory reaches zero | Red icon |
### Health Status Indicators
| Status | Condition | Color |
| ------------ | ----------------------------------------- | ----------- |
| **Healthy** | More than 30 days of stock remaining | Green pill |
| **Warning** | Between 14 and 30 days of stock remaining | Yellow pill |
| **Critical** | Fewer than 14 days of stock remaining | Red pill |
### Forecast Chart
The chart displays:
* **Blue solid line:** Actual historical stock levels
* **Gray solid line:** Historical daily sales rate
* **Orange dashed line:** Projected future stock depletion
* **Red dotted line:** Stockout threshold (zero inventory)
You can:
* **Hover** over any point to see the exact date and stock level
* **Zoom** in or out to focus on specific time periods
* Click **"Reset Zoom"** to return to the default view
{% hint style="success" icon="rocket" %}
**Pro Tip:** If you have a 60-day lead time from your supplier, set your reorder point at the 60-day mark on the forecast chart. When the projected stock line crosses that point, it is time to place your reorder.
{% endhint %}
***
## Inventory Alert Rules
Inventory Alert Rules let you configure automatic notifications when stock levels reach critical thresholds.
### Accessing Alert Rules
1. Open the **Product Batches modal** for any product.
2. Click the **gear/settings icon** in the modal header.
3. The Inventory Rules modal opens.
### Configurable Rules
| Rule | Description | Recommended Setting |
| ------------------ | ----------------------------------------------- | --------------------------------------- |
| **Out of Stock** | Alert when stock reaches exactly 0 units | Enable for all products |
| **Low Inventory** | Alert when stock drops below a custom threshold | Set to your average 14-day sales volume |
| **Restock Needed** | Alert when stock drops below your reorder point | Set to cover your supplier lead time |
### Setting Up a Rule
1. Open the Inventory Rules modal.
2. For each rule section, toggle the rule **on/off**.
3. Set the **threshold value** (number of units).
4. Select the **marketplace** the rule applies to (or "All").
5. Click **"Save Rules"** to activate.
{% hint style="info" %}
Inventory alerts are delivered through SellerMagnet's notification system. Make sure your notification preferences are configured in **Settings > Notifications** to receive email or in-app alerts.
{% endhint %}
***
## ๐ฏ Real-World Scenario: Managing a Product Launch
**Situation:** You are launching a new product with 1,000 units of initial inventory at EUR 3.20 per unit.
| Step | Action |
| ---- | --------------------------------------------------------------------------------------------------------------------------------- |
| 1 | Navigate to **Products Management** and locate the new product (it appears automatically once listed on Amazon) |
| 2 | Open the **Product Batches modal** for the product |
| 3 | Create a new batch: Total Units = 1000, Unit Net Cost = EUR 3.20, plus any tax/shipping/customs costs, Arrival Date = launch date |
| 4 | Set up **Inventory Alert Rules**: Low Inventory at 200 units, Restock at 350 units |
| 5 | After 2 weeks, check the **Stock Forecast** to see daily usage trends |
| 6 | If daily usage is 15 units/day and supplier lead time is 30 days, you need to reorder when stock hits 450 units (15 x 30) |
**Before batches:** Dashboard shows EUR 12,480 profit on the product (misleading, just revenue minus fees). **After batches:** Dashboard shows EUR 5,280 real profit (revenue minus fees minus EUR 3,200 COGS).
***
## Managing Multiple Batches
When you reorder inventory at different prices, you accumulate multiple batches per product. SellerMagnet handles this using a **FIFO (First In, First Out)** approach by default. You can also assign an average price across all batches for orders not covered by a specific batch's time period:
| Batch | Qty | Price/Unit | Date |
| ------- | --- | ---------- | ---------- |
| Batch 1 | 500 | EUR 3.20 | 2026-01-10 |
| Batch 2 | 300 | EUR 3.45 | 2026-03-05 |
| Batch 3 | 700 | EUR 2.95 | 2026-04-01 |
As orders come in, COGS are allocated from the earliest batch first. Once Batch 1's 500 units are depleted, COGS automatically shift to Batch 2's price.
{% hint style="warning" %}
If you delete an earlier batch, the COGS allocation shifts to the next available batch. This can retroactively change profit calculations for historical orders. Always use Edit instead of Delete when correcting batch data.
{% endhint %}
***
โ ๏ธ Common Mistakes to Avoid
| Mistake | Impact | Better Approach |
| ------------------------------------ | ---------------------------------------------------------- | ----------------------------------------------------------------- |
| Not creating batches for any product | All profit numbers are wrong across the entire platform | Make batch creation part of your receiving workflow |
| Using one batch for all inventory | Cannot track price changes or calculate accurate FIFO COGS | Create a new batch for each purchase order |
| Entering COGS in the wrong currency | Over/understated costs | Always enter prices in your SellerMagnet base currency |
| Ignoring the Stock Forecast | Running out of stock leads to lost sales and ranking drops | Check forecasts weekly for your top products |
| Setting alert thresholds too low | Alerts arrive after it is too late to reorder | Set thresholds that account for supplier lead time + safety stock |
| Deleting batches to "fix" data | Destroys historical COGS records | Edit the batch instead of deleting and recreating |
\## โ
Best Practices
1. **Create batches immediately** when inventory is received, not when it starts selling.
2. **Record all cost components** per unit: net cost, tax, shipping, payment fees, and customs/import duties. This ensures your COGS reflect true landed cost.
3. **Use notes** on batches to track supplier names, PO numbers, or volume discounts.
4. **Review stock forecasts weekly** for your top 20 revenue-generating products.
5. **Set inventory alerts** for every product with more than 10 units/day sales velocity.
6. **Audit COGS quarterly** by comparing your batch records against supplier invoices.
***
## Exporting Products
The **Export** button (download icon) in the table toolbar downloads your catalog for use in spreadsheets or for editing and re-importing. Click it to choose a format:
| Format | Use it for |
| --------- | ----------------------------------------------------------------- |
| **CSV** | Editing in any spreadsheet tool, or preparing a file to re-import |
| **Excel** | A ready-to-open `.xlsx` workbook |
* If **no products are selected**, the export covers your **whole catalog** (respecting the current view).
* If you have **selected rows** with the checkboxes, a small dialog asks whether to export **all products** or **only the selected ones**.
{% hint style="info" %}
The export uses the **same column layout as the import template**, so the fastest way to bulk-edit COGS is: export -> edit the cost columns in a spreadsheet -> re-import.
{% endhint %}
***
## Bulk Import (CSV)
Instead of entering batches one product at a time, you can update many SKUs at once with the **Import** button (upload icon) in the toolbar. It opens a guided **3-step wizard**.
{% stepper %}
{% step %}
### Upload
Drop a **CSV file** onto the upload area (or click to browse). Two helpers sit above it:
* **Download Template** - a blank CSV with the correct headers.
* **Export Current Products** - exports your existing catalog so you can edit real values and re-upload.
The wizard lists the **expected headers**. Products are matched by **`sku` + `amazon_marketplace`**, and the file can carry the latest batch and shipping data per SKU:
| Column | Meaning |
| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| `sku` | Your seller SKU (required for matching) |
| `amazon_marketplace` | Marketplace the SKU belongs to (required for matching) |
| `returns_sellable` | Whether returns go back into sellable stock |
| `shipping_country_pricing_net_cost_in_cents` / `shipping_currency` | Per-unit shipping cost and its currency |
| `latest_batch_name` | Name of the batch to create/update |
| `latest_batch_total_units` | Units in the batch |
| `latest_batch_unit_net_cost_in_cents` | Net cost per unit (in **whole cents**, e.g. `475` = 4.75) |
| `latest_batch_unit_tax_cost_in_cents` | Tax per unit (cents) |
| `latest_batch_unit_shipping_cost_in_cents` | Inbound shipping per unit (cents) |
| `latest_batch_unit_payment_cost_in_cents` | Payment fee per unit (cents) |
| `latest_batch_unit_customs_cost_in_cents` | Customs/duty per unit (cents) |
| `latest_batch_unit_additional_cost_in_cents` | Any other per-unit cost (cents) |
| `latest_batch_currency` | Currency of the batch costs |
| `latest_batch_arrival_date` | Date the inventory arrived |
| `simple_unit_cost_in_cents` | *Optional.* Sets an **Easy-mode flat cost per unit** (whole cents, e.g. `800` = 8.00) that overrides inventory batches for that SKU |
| `simple_cost_currency` | *Optional.* Currency for the flat cost; defaults to the marketplace currency |
{% hint style="warning" %}
All cost columns are in **whole cents**, not decimal currency. Enter `800` for a cost of 8.00. Make sure your date format matches the format shown in the wizard.
{% endhint %}
{% endstep %}
{% step %}
### Validation
Every row is checked and tagged **Valid**, **Warning**, or **Error**. From this screen you can:
* Filter to **Errors**, **Warnings**, or **Valid** rows.
* **Edit** cells inline, or **bulk-edit** a value across selected rows.
* **Delete** rows you do not want to import.
* **Export error rows** to fix them in a spreadsheet and re-upload.
{% endstep %}
{% step %}
### Import
A final review shows totals (ready to import, warnings, errors that will be skipped) and a marketplace breakdown. Confirm to apply the changes.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Import **updates existing products** (matched by SKU + marketplace) with new batch, flat-cost, and shipping data. It does **not create new products** - listings appear in SellerMagnet automatically once they are live on Amazon.
{% endhint %}
### Loading several batches for the same product
You are not limited to one batch per SKU. To import **multiple purchase lots for the same product in a single file, add one row per batch**: repeat the same `sku` + `amazon_marketplace` on each row and give every row a **different `latest_batch_name`** with its own units, costs, and arrival date. Each unique batch name becomes its own lot, so a SKU with three restocks is simply three rows.
{% hint style="warning" %}
Two details matter when you do this:
* **The batch name is the key.** Reusing an existing `latest_batch_name` for a SKU **updates that lot** instead of adding a new one. Leaving the name blank falls back to a default (`SM Batch `), so several blank-named rows on the same day collapse into one lot - always give each batch a distinct name when loading more than one.
* **Expect a duplicate warning.** The Validation step tags repeated `sku` + `amazon_marketplace` rows with a **"Duplicate SKU + Marketplace"** warning. When you are intentionally loading several batches this is expected - it is a heads-up, not an error, and the rows still import.
{% endhint %}
***
## Comparison: Products Table vs. Ordered Products
| Feature | Products Management | Ordered Products (Orders section) |
| ---------------------------- | ----------------------- | --------------------------------- |
| **Focus** | Full catalog management | Sales performance analysis |
| **Includes unsold products** | Yes | No (only products with orders) |
| **Batch/COGS management** | Yes (primary purpose) | No (read-only COGS display) |
| **Stock Forecast** | Yes | No |
| **Inventory Alerts** | Yes | No |
| **Tag filtering** | Via Products | Yes (filter by tags) |
| **Financial breakdown** | Basic P\&L per product | Detailed per-order breakdown |
***
## โ FAQ
How does SellerMagnet calculate COGS when I have multiple batches?
SellerMagnet uses FIFO (First In, First Out) allocation by default. The oldest batch's cost is used first. When that batch is fully depleted, it moves to the next batch chronologically. For orders not covered by any batch's time period, you can also assign an average cost across all batches.
Can I import batch data in bulk?
Yes. Use the **Import** button in the products toolbar to run the **3-step CSV wizard** (Upload -> Validation -> Import). Download the template (or export your current products), fill in the batch and cost columns, and re-upload. You can also set an Easy-mode flat cost per SKU via the optional `simple_unit_cost_in_cents` column. To load **several batches for one SKU**, add one row per batch with the same SKU + marketplace and a different `latest_batch_name` - see [Loading several batches for the same product](#loading-several-batches-for-the-same-product). Products are matched by SKU + marketplace and updated in place; import does not create new products.
What if I sell the same product on multiple marketplaces?
Create batches at the product level (per ASIN/SKU). The batch data applies across all marketplaces where that product is sold. Inventory alert rules can be set per marketplace.
How accurate is the Stock Forecast?
The forecast uses a 30-day rolling average of daily sales to project future depletion. Accuracy depends on sales consistency. Products with highly seasonal or promotional sales patterns may see less accurate forecasts.
Can I set different alert thresholds per marketplace?
Yes. When configuring inventory alert rules, you can select a specific marketplace or set rules that apply to all marketplaces.
What happens if I forget to create a batch for a product?
The product will show EUR 0.00 for COGS, which means all revenue minus Amazon fees appears as "profit." This overstates your actual profitability. We recommend creating batches for all products.
Does the stock level update in real time?
Stock data is synced from Amazon's API and typically updates multiple times per day. There may be a delay of a few hours between an actual stock change in Amazon and the reflected value in SellerMagnet.
***
## โก๏ธ What's Next?
{% content-ref url="/pages/xy8uixvNORGWL0LqDzwf" %}
[Product Tags](/dashboard-and-analytics/dashboard-overview/product-tags.md)
{% endcontent-ref %}
{% content-ref url="/pages/3gqW20LoOHjYA4o7jTeF" %}
[Listing Performance](/dashboard-and-analytics/dashboard-overview/listing-performance.md)
{% endcontent-ref %}