Skip to main content
A price level is one list of selling prices, for example Retail or Wholesale. Every product can have one price at each level. Open Catalog > Price Levels (/catalog/price-levels) to see your levels, create new ones and choose who sets their prices. You need the Price levels permission to see the page, and its Create, Update and Delete children to add, change and delete levels.

​
The list

The Actions menu on a row has Edit, Delete and Change owner.

​
Create a price level

1

Open the form

Click New Price Level.
2

Fill it in

  • Name: required.
  • Set as Recommended Retail Price: only one price level per organization can be marked as the recommended retail price.
  • Who sets prices shows Omnilinker · Catalog: “New price levels are set in Omnilinker. You can change who sets them afterwards.”
  • Currency: every price stored at this level must be in this currency. Not declared leaves it open. Declaring a currency is refused while a stored price is in another currency, and a declared currency cannot be cleared afterwards.
  • Audience: Retail (consumers) prices are entered gross, Business (B2B) prices net. The recommended retail price level is always retail.
  • Country: two letters, for example PL or DE. It labels the level and suggests its VAT rate.
  • Default VAT (%): the rate a new price at this level starts with. Leave it empty for the usual rate.
3

Save

Click Save.

​
Who sets a level’s prices

Each price level has one owner, the system whose prices count for it:
  • Omnilinker · Catalog: “Your team and your repricer rules set these prices in Omnilinker.” Every new level starts here.
  • Managed by another system: another system, such as a shop or a PIM, sets these prices. “Omnilinker neither reads nor writes ‹level›: Catalog shows its prices read-only and repricer rules can’t set it.”
  • An ERP connection: the ERP sets the prices of the products linked to it. “‹connection› sets these prices: Catalog shows them read-only for the products linked to it.” The other products keep Omnilinker’s prices. The option is offered only when the connection can set the level, and otherwise it is locked with the reason, for example “Reading prices from ‹connection› is switched off for this account.” (the feature Read prices from the ERP is off until Omnilinker switches it on), “Waiting for the first full read of prices from ‹connection›. It usually arrives within minutes.”, “This price level no longer exists in ‹connection›, or it was ignored. Map it again …”, “This isn’t mapped on ‹connection›…” or “The connection ‹connection› is switched off. Switch it on first.” The level also needs a Currency. See Prices from your ERP.
People and repricer rules write only the levels Omnilinker owns. A repricer rule is never an owner: it writes prices on Omnilinker’s behalf.

​
Change who sets a level’s prices

You need the Change who sets price levels permission, under Price levels.
1

Open the dialog

Open the level’s Actions menu and click Change owner. The dialog Who sets ‹level› shows the current owner, since when and who chose it, for example “Since 09:57 · Anna Kowalczyk”, as the ERP pages name it. Where no person can be named, it says how the owner came to set the level instead, for example “Since your catalog was set up”.
2

Choose the owner

Pick Omnilinker · Catalog, Managed by another system or an ERP connection. Under What changes now, Omnilinker lists what the change does, for example:
  • “1 repricer rule writing ‹level› stops setting it.”
  • “Marketplaces keeps sending ‹level›‘s current prices to its listings; they stop changing.”
  • “3 calculated bundle prices become fixed prices.” A bundle price that follows its components keeps its current amount as its own.
  • “2 sends to an ERP are already queued at this level.” They are still delivered, except when you hand the level to that ERP: then “3 prices waiting for ‹ERP› will be withdrawn. This cannot be undone.” and the dialog also counts the prices that will replace Omnilinker’s. See Prices from your ERP.
  • Back to Omnilinker: “Catalog and repricer rules can set ‹level› again; listings that use ‹level› start receiving its prices.”
3

Confirm

Click Mark as managed by another system, Make Omnilinker · Catalog the owner or Make ‹ERP› the owner. An ERP takes the level over in steps, shown in Handing the level over. When you hand a level Omnilinker sets to an ERP, you can also choose under Start from to write Omnilinker’s prices to the ERP first, with Write prices to ‹ERP›, then hand over; see Start from Omnilinker’s prices.
While a level is being handed to an ERP from Omnilinker’s prices, its row on Price Levels says where the handover stands, for example “Handing over to ‹ERP›: every price is written, ‹ERP› takes over shortly.” or “Handover to ‹ERP› waits for your decision: 3 prices were not written.”, with Open the handover. If something changed at the level while the dialog was open, such as who sets it or a price sent from it to an ERP, Omnilinker says “Something changed at the price level ‹level› a moment ago, such as who sets it or a price sent from it to an ERP. Reload and try again.”

​
What changes when another system manages a level

  • On a product’s Prices and margin, the level’s price is read-only and marked Managed by another system, with Why can’t I edit this?. See Prices you cannot edit.
  • A bulk edit refuses the level: “Prices at ‹level› are managed by another system, so a bulk edit can’t change them.”
  • A price import skips the level’s rows as Skipped: set by another system. See Import prices.
  • Duplicating a product does not copy its price at that level: “Prices managed by another system were not copied: ‹levels›”.
  • Repricer rules that write the level stop setting it, their pending recommendations at the level are cancelled, and each rule’s people get one notice in their inbox with the ways to fix it. See Rules and other systems’ price levels.
  • Send to ERP does not send the level’s prices: “Another system manages this price level, so Send to ERP does not write its prices.”
When the level is Omnilinker’s again, all of this is lifted and the inbox notices clear.

​
When an ERP sets a level

The prices of the products linked to the ERP are read-only, marked “Comes from ‹ERP›” with how long ago they were read (no age is shown while Read prices from the ERP is off), and the products not linked keep their editable prices. Repricer rules writing the level skip the linked products, and Send to ERP does not write the level back to that ERP: “Prices on ‹level› come from this ERP connection, so Send to ERP does not write them back.” See Prices from your ERP.

​
When the ERP changes a level Omnilinker sets

If a price on the ERP level mapped to a level Omnilinker sets is changed in the ERP, Omnilinker keeps its own prices and reports it. The row shows “Differs in ‹ERP›: 6 · found 14:05”; to hand the level to the ERP, use the row’s Change owner action, which opens the dialog above. The inbox gets a notice. See A level Omnilinker keeps.

​
Who last set a price

Omnilinker records who writes every selling price: a person on the product page, a bulk edit, an Excel import, an API key, a repricer rule, a bundle recalculation or an owner change. A product’s Prices and margin shows it under each price, and its Selling price history lists every change. Prices written before this was recorded show no writer. See Selling prices and their history.

Products

Edit a product’s prices and see who set them.

Rules and templates

Choose the price level a repricer rule writes.

Prices to your ERP

Write Omnilinker’s prices into your ERP.

Lists and mappings

Map your price levels to the ERP’s.