---
title: "Place products on markets and track authorizations"
description: "Record which version of a product is sold in each market and under which name, move placements through their lifecycle, and keep the regulatory authorizations behind each placement current with expiry reminders."
url: https://helpcenter.complytrain.net/en/articles/178-place-products-on-markets-and-track-authorizations
collection: "Markets and qualification"
updated: 2026-09-22
language: en
---

# Place products on markets and track authorizations

Record which version of a product is sold in each market and under which name, move placements through their lifecycle, and keep the regulatory authorizations behind each placement current with expiry reminders.

Record which version of a product is sold in each market and under which name, move placements through their lifecycle, and keep the regulatory authorizations behind each placement current with expiry reminders.

A market record says that one version of a product is sold in one market, under a particular name. Each market can carry a different version: Germany can be on version 2.0 while Denmark is still on 1.0 because its approval is pending. The authorizations that make a placement lawful, such as a CE certificate or a national approval, are recorded against the placement and raise reminders before they expire.

A product sold in a single market needs no market records at all. Add them when you sell in more than one market, sell under different names, or need to track authorizations per market.

## Who can do this

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Action</p></th><th colspan="1" rowspan="1"><p>Who</p></th></tr><tr><td colspan="1" rowspan="1"><p>See markets and authorizations</p></td><td colspan="1" rowspan="1"><p>Anyone with <strong>View Products</strong> (<code>product-library:view</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Add, place, suspend, withdraw, edit or delete placements</p></td><td colspan="1" rowspan="1"><p><strong>Manage Markets and Authorizations</strong> (<code>product-library:manage-markets</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Add, edit or remove authorizations</p></td><td colspan="1" rowspan="1"><p><strong>Manage Markets and Authorizations</strong> (<code>product-library:manage-markets</code>)</p></td></tr></tbody></table>

Admins can do all of these. Buttons appear only for people who can use them. Placements and authorizations follow the product's classification, so you see only the records your clearance allows; see [clearances](https://help.complytrain.net/en/product-library/clearances/).

## Open the Markets tab

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

1.  Open **Products** and choose the product in the **Product register**.
    
2.  Choose the **Markets** tab.
    

The tab covers the whole product, not only the version selected above it, and says so with the badge **All versions**. The selected version matters only when you add a market: the button reads **Add market for** followed by the version label, for example **Add market for 2.0**. To add a market for a different version, select that version first.

On a new product, the **Overview** tab also offers **Say where it is sold** under **Getting this product on its feet**. It opens the **Markets** tab.

## Add a market

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

1.  Select the version you want to place, then choose **Add market for** the version.
    
2.  Complete the fields below.
    
3.  Choose **Save**.
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What it does</p></th><th colspan="1" rowspan="1"><p>Rules and defaults</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Market</strong></p></td><td colspan="1" rowspan="1"><p>The country or region group the version is sold in. Region groups are listed first, then countries, each as name and code, for example "Denmark (DK)".</p></td><td colspan="1" rowspan="1"><p>Required. A region group such as the EU is a market in its own right; placing a version on it does not place it on each member country.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Marketed name</strong></p></td><td colspan="1" rowspan="1"><p>The name the product is sold under in this market.</p></td><td colspan="1" rowspan="1"><p>Optional, up to 255 characters. Leave it blank to use the register name.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Place on the market now</strong></p></td><td colspan="1" rowspan="1"><p>Records the version as on the market today instead of planned.</p></td><td colspan="1" rowspan="1"><p>Off by default. Not offered for a draft version, which shows "This version is a draft, so it can only be planned for a market, not placed on one."</p></td></tr></tbody></table>

A new row starts as **Planned**, or as **On the market** when you ticked **Place on the market now**. If you choose **Save** without a market, the page says "Choose a market first."

![The example selects Denmark and a marketed name. Draft version 1.0 can be planned, but is not yet placed on the market.](https://staticfiles.gleap.io/p6950dfbf97796f2087a9f022/o6opwwieTI6P9pOykhThHNvZVAu989RplYvWcg86rRhjQBXWcfNw29K5A38bEX5lS61n36GRRmN.png "Plan a market for a draft configuration")

## Read the markets table

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Column</p></th><th colspan="1" rowspan="1"><p>Shows</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Market</strong></p></td><td colspan="1" rowspan="1"><p>The market name, with its code underneath.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Marketed name</strong></p></td><td colspan="1" rowspan="1"><p>The name used in this market, or "Sold under the register name".</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Version</strong></p></td><td colspan="1" rowspan="1"><p>The version this placement is for.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Status</strong></p></td><td colspan="1" rowspan="1"><p><strong>Planned</strong>, <strong>On the market</strong>, <strong>Suspended</strong> or <strong>Withdrawn</strong>. A withdrawn row also shows the reason.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Authorizations</strong></p></td><td colspan="1" rowspan="1"><p>The number of authorizations. Choose it to open them. A red badge such as "1 expired" counts authorizations past their expiry date.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Actions</strong></p></td><td colspan="1" rowspan="1"><p>The actions the current status allows.</p></td></tr></tbody></table>

If any placement that has not been withdrawn carries an expired authorization, a red alert appears above the table: **An authorization has expired**. It counts the affected placements and asks you to renew the authorization or withdraw the placement.

With no market records, the tab reads "No markets recorded. A product sold in a single market needs none."

![The saved row retains the marketed name, version 1.0, Planned status and authorisation count.](https://staticfiles.gleap.io/p6950dfbf97796f2087a9f022/wt9xDMisNxcvJndGus0KNHsw42cuDqvTRqWwi6YutW4HhVBeV5gYB5nF1dvGl0hwq2gYdf79iVH.png "Inspect the planned market record")

## Placement lifecycle

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Status</p></th><th colspan="1" rowspan="1"><p>Meaning</p></th><th colspan="1" rowspan="1"><p>Actions offered</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Planned</strong></p></td><td colspan="1" rowspan="1"><p>You intend to sell this version here, for example while approval is pending.</p></td><td colspan="1" rowspan="1"><p><strong>Place</strong>, <strong>Delete</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>On the market</strong></p></td><td colspan="1" rowspan="1"><p>The version is being sold here. Only one version of a product can be on the market in a given market at a time.</p></td><td colspan="1" rowspan="1"><p><strong>Suspend</strong>, <strong>Withdraw</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Suspended</strong></p></td><td colspan="1" rowspan="1"><p>Temporarily off the market, for example during a field action.</p></td><td colspan="1" rowspan="1"><p><strong>Place</strong>, <strong>Withdraw</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Withdrawn</strong></p></td><td colspan="1" rowspan="1"><p>Permanently off this market. The row is kept as the record of what was sold where and when.</p></td><td colspan="1" rowspan="1"><p>None</p></td></tr></tbody></table>

A withdrawn placement cannot be placed again. To return to that market later, add a new market record; re-entering a market is a new event, not an undo.

## Place a version on a market

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

1.  Find the **Planned** or **Suspended** row for the version.
    
2.  Choose **Place**.
    

The version must have been released; a draft version can only be planned. A planned placement is dated today when you place it; a suspended one keeps its original date.

If another version of the same product is on the market there, it is withdrawn in the same step. Its row changes to **Withdrawn** with the reason "Superseded on this market by version" followed by the new version label, so the table shows when the market changed hands. The same happens when you add a market with **Place on the market now** ticked.

Placing and withdrawing are passed on to connected modules. When a version enters a market, Media Monitoring can propose extending a market watch to cover it. When a version leaves a market, organisations linked to the product, such as a notified body or distributor, are flagged as needing to be told. Both appear as proposals under **What this change affects** on the **Bill of materials** tab; see [change impact](https://help.complytrain.net/en/product-library/connections-change-impact/).

## Suspend or withdraw a placement

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

To suspend, choose **Suspend** on a row that is **On the market**. No reason is needed, and **Place** returns it to the market.

To withdraw:

1.  Choose **Withdraw** on a row that is **On the market** or **Suspended**.
    
2.  In **Why is the product coming off this market?**, record the reason: a recall, a safety finding, a commercial exit or a lapsed authorization. A regulator reads this first.
    
3.  Choose **Withdraw from market**.
    

The reason is required, up to 4,000 characters, and is kept permanently. Without one, the page says "A reason is required to withdraw from a market."

## Correct or delete a placement

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

Edit a placement to correct its marketed name or the date it went on the market. The version and the market cannot be changed; record a new placement instead.

Only a **Planned** row can be deleted: choose **Delete**, then confirm **Delete this planned placement?**. Nothing was ever placed, so no regulatory record is lost. Deleting is refused while the plan still carries authorizations; remove them first. It is also refused when the row is the product's last market record and more than one version is still in service, because outside market records only one version can be current; withdraw or supersede the extra versions first.

## Record an authorization

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

1.  In the **Authorizations** column, choose the count for the placement. The panel **Authorizations for** the market opens under the row.
    
2.  Complete the fields below.
    
3.  Choose **Add authorization**.
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What it does</p></th><th colspan="1" rowspan="1"><p>Rules</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Type</strong></p></td><td colspan="1" rowspan="1"><p>The kind of authorization, for example a CE certificate or FDA clearance.</p></td><td colspan="1" rowspan="1"><p>Required, up to 60 characters. When the product's profile lists authorization types, you choose from that list; otherwise you type the type.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Conformity route</strong></p></td><td colspan="1" rowspan="1"><p>How conformity was shown, for example "Annex IX" or self-declaration.</p></td><td colspan="1" rowspan="1"><p>Optional, up to 120 characters.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Certificate number</strong></p></td><td colspan="1" rowspan="1"><p>The certificate or approval reference.</p></td><td colspan="1" rowspan="1"><p>Optional, up to 200 characters. The same type and certificate number cannot be recorded twice on one placement.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Expires</strong></p></td><td colspan="1" rowspan="1"><p>The date the authorization lapses.</p></td><td colspan="1" rowspan="1"><p>Optional. Setting a date raises a reminder before the authorization lapses.</p></td></tr></tbody></table>

Each authorization shows its type, certificate number, conformity route, issuing body and expiry date, with a badge: **Active** (green), amber when it expires within 30 days, **Expired** in red once the date has passed, or **Suspended** or **Withdrawn**.

## Keep authorizations current

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

Edit an authorization to record what changes over its life: a renewed expiry date, the issue date, the issuing body (an organisation in the [stakeholder register](https://help.complytrain.net/en/vendor-management/register-import-stakeholders/)), notes, or a new status. Changing the status to suspended or withdrawn needs a reason, because a lapse and a revocation are very different facts. Editing the expiry date also re-arms its reminder.

Use the bin button (**Remove authorization**) only for a record entered in error. The confirmation **Remove this authorization?** reminds you that an authorization that was ever relied on should be withdrawn instead, so its history survives.

## Expiry reminders

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

Every morning at 07:00, Products looks for dates that are about to pass and sends an in-app notification:

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>What expires</p></th><th colspan="1" rowspan="1"><p>Notification type</p></th><th colspan="1" rowspan="1"><p>Reminders start</p></th></tr><tr><td colspan="1" rowspan="1"><p>An active authorization on a placement that is on the market or suspended</p></td><td colspan="1" rowspan="1"><p>Market Authorization Expiring</p></td><td colspan="1" rowspan="1"><p>90 days before the expiry date</p></td></tr><tr><td colspan="1" rowspan="1"><p>A passed test result on a draft or released version</p></td><td colspan="1" rowspan="1"><p>Test Qualification Expiring</p></td><td colspan="1" rowspan="1"><p>180 days before its <strong>Valid until</strong> date</p></td></tr><tr><td colspan="1" rowspan="1"><p>An active export licence</p></td><td colspan="1" rowspan="1"><p>Export Licence Expiring</p></td><td colspan="1" rowspan="1"><p>120 days before it expires</p></td></tr></tbody></table>

The reminder goes to the product's regulatory contact, or to its owner when no regulatory contact is recorded. Set both on the product; see [maintain a product](https://help.complytrain.net/en/product-library/maintain-product/). A product with neither gets no reminders, so make sure every product that carries an expiry date has one of them.

The notification names the product, the marketed name, the version, the market, the certificate number and the issuing body, and links to the product. It is sent at most once a day for each record, and repeats each morning until the expiry date is moved beyond the reminder period, the authorization is suspended or withdrawn, or the placement is withdrawn. It is high priority within 30 days of expiry and urgent once the date has passed. These types are mandatory: nobody can switch them off in their notification preferences. See [your notifications](https://help.complytrain.net/en/settings/my-notifications/).

## Different versions on different markets

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

Once a product has any market records, releasing a new version no longer takes the previous version out of service. Each market keeps the version placed on it until you place another one there. This is how one market can stay on 1.0 while another moves to 2.0.

Tenders use these records. When a bid names a version and a market, the Tender's **Products** tab shows the marketed name recorded for that market, and **Propose answers** can offer the marketed name and the placement's authorizations as answers to the tender's requirements. See [claims](https://help.complytrain.net/en/product-library/claims/#use-claims-in-a-tender) for how bids draw on product records.

## Example: move Germany to version 2.0

Product location: `/products/{productId}/markets` (fallback: `/products`). Open the product in Products, then choose the Markets tab. Select the version first when you add a market.

Your organisation sells the product as version 1.0 in Germany (DE) and Denmark (DK). Version 2.0 has been released and its CE certificate has arrived for Germany only.

1.  Select version 2.0 and choose **Add market for 2.0**. Choose Germany (DE) and choose **Save**. The row is **Planned**.
    
2.  Open its **Authorizations**, enter the **Type**, **Certificate number** and **Expires** date, and choose **Add authorization**.
    
3.  Choose **Place** on the 2.0 row for Germany. The 2.0 row is **On the market**, and the 1.0 row for Germany changes to **Withdrawn**, "Superseded on this market by version "2.0"".
    

Denmark stays on 1.0 until its approval arrives. Ninety days before the German certificate expires, the regulatory contact starts receiving **Market Authorization Expiring** reminders.
