Products

Products are what you sell. Open Catalog > Products to see them, create new ones and edit or delete existing ones. Each product has a SKU, a name and, optionally, a GTIN, a brand, invoice details, a size and weight, selling prices and a purchase price.

​

Create and edit a product

Click + New product above the list to create a product. The SKU and Name are required; the Invoicing card takes the invoice details below, and the other cards the organisation, the RRP and cost, and the size and weight. Click a product in the list to open it beside the list, or Open full page to give it a page of its own. Click the SKU, MPN or GTIN under its name to copy it. Its Details show the identity (Name, SKU, MPN, GTIN), the organisation, Invoicing and Logistics. Click Edit (or press E) to change them, then Save (Ctrl+S). Prices and the purchase cost are edited on Pricing. See Purchase prices and history.

​

Invoice details

Three fields, on the Invoicing card, describe how the product appears on an invoice. All are optional.

​

Product images

Open a product’s Media tab (in the panel beside the list or on its full page) and drop images anywhere on it, paste a copied image with Ctrl+V, or click Add images: JPEG, PNG or WebP, up to 25 MB each, 10 at a time and 20 per product. Files are added in file-name order (photo-2 before photo-10), after the images already there. A file that can’t be added is listed with the reason. A JPEG photo over 25 megapixels or 12,000 pixels a side is scaled down to fit them (up to 100 megapixels and 30,000 pixels a side; a larger one is refused), and a PNG or WebP that large is refused. Every image is stored as WebP, the right way up, without the photo’s own data (camera, location). Its colour profile is kept, so a photo taken on an iPhone or a camera set to Adobe RGB keeps its colours. The first image is the main one: the product list and the product’s header show it. Drag an image to move it, or focus its handle and use the arrow keys; Make main moves an image to the first place. Every image shows whether it has alt text (ALT) or not (NO ALT), and missing alt text above the images shows only those. Click an image to describe it, or switch to List to describe them all in one place. Right after you add images, the tab asks you to describe them; you can skip that. Alt text is saved when you leave the field. Remove takes an image away at once, with Undo to bring the same image back in the same place, with its alt text, for an hour; only the last removal can be undone. Each change is saved at once. If someone else changed the product’s images since you opened it, Make main and Remove say so instead of overwriting their order. You need permission to edit products, and images can’t be changed while another section is being edited: save or cancel that edit first. Click a product’s thumbnail, in the list, beside the list or on its full page, to see all its images full size: the main one first, with its alt text, zoom, and ← → or the strip below to move between them. Edit in Media takes you to the Media tab, and an image with no alt text says so there. A thumbnail with a number shows how many images the product has; one with + opens Media to add the first.

​

Images from your ERP

A linked product’s images can come from your ERP, when the connection’s Images field is on: see Product images. The Media tab then says “Images come from ‹ERP›, replaced when ‹ERP› changes them. Your own images stay after them.”, and each image from the ERP carries the badge From ‹ERP›. Nothing is locked: you can still move, describe, remove and add images.

• When an image changes in the ERP, it is replaced in its place, with its alt text. An image deleted in the ERP is removed. Your own images are never replaced or removed, and stay after the ERP’s.
• Remove on an image from the ERP keeps it out: “Image ‹n› removed here. It comes back if ‹ERP› changes this image.” If the ERP later changes that image, the new version is added.
• Undo brings it back, as for any image. If the ERP has meanwhile sent the image again in a newer version, which is already on the product, Undo is refused: “This image came back from the ERP meanwhile, in its newer version. It is already on the product, so there is nothing to undo.”
• Your own order stays until the ERP changes its order, for example its main image; then the ERP’s images move to the front again, in the ERP’s order.

​

Product type

Every product has a type. Choose it with Product type in the product’s Details while you edit, and with Start from when you create one. A Manufactured product can be a component of a bundle, like a Simple one. A bundle cannot be a component of another bundle. Changing the type of an existing product:

• Simple Product and Manufactured Product change into each other with no other effect: only the label changes.
• A bundle changing to Simple Product or Manufactured Product loses its components, and prices that followed them keep their current amounts as their own. A bundle’s components are never turned into a bill of materials.
• A product can become a Bundle Product only if it has no stock and no open order holds. If it has quantity on hand or reserved in any warehouse, or orders still hold stock of it, Omnilinker refuses and lists what it found, for example “Stock: 5 on hand, 1 reserved; Open order holds: 2”. A bundle has no stock of its own, so move or sell the stock first. A product that is a component of another bundle cannot become a bundle either.

​

Selling prices and their history

A product’s selling prices are on Pricing, under Prices and margin: one row per price level, with the net and gross price, the VAT, and the margin and markup against the purchase cost. Click Edit prices (or press E) to change them. Under each price, a line says who last set it, for example “Last set 12 Oct 14:05 by Anna Nowak”, “Last set 12 Oct 14:05 by Anna Nowak · Excel import”, ”… · bulk edit”, ”… through an API key”, “Last set 12 Oct 14:05 by Repricer rule “Allegro min”” or “Recalculated from bundle components 12 Oct 14:05”. Omnilinker records who wrote each price since this version; on a product with older prices, “Who set each price is shown for changes made since this version.” says so.

​

When a repricer rule sets the price

When a repricer rule covers the price, its row says which rule sets it next and what that run does: “In Repricer rule “Allegro min” · next run 14:00 proposes a new price”, ”… recalculates it” for a rule that applies prices itself, or “no run scheduled”. “+2 more rules” says that other rules cover it too, and “until ‹date›” that the rule stops then. The rule’s name links to the rule. When several rules on the same price level cover the product, the one with the higher priority sets the price; see When two rules cover the same product. If this cannot be read, the section says “Repricer information is unavailable right now”, and you can still edit. You can still change a price a rule covers. Your price is saved, and the rule may set it again at its next run. To stop that, keep your price out of the rule.

​

Keep my price

Keep my price, under a price a repricer rule sets, keeps that product out of the rule: the rule skips it and its current price stays. You need Keep product prices out of repricer rules or Edit rules, both under Pricing Intelligence > Repricer. Without them the button is disabled: “Ask someone who can edit repricer rules”. When the rule you kept it out of is the only one covering the product, the row then says “Kept through 31 Oct: Repricer rule “Allegro min” skips it” or “Kept until someone releases it: …”. If another rule on the same level covers the product, it takes over and the line names both: “Kept out of Repricer rule “Allegro min” until someone releases it · Repricer rule “Floor” next run 15:00 proposes a new price”. The button becomes Change, where you can change the date or Release the product. After the date you chose, the product is back in the rule. The rule’s editor lists its kept products; see Kept products.

​

Prices you cannot edit

A price at a level that another system manages is read-only (see Who sets a level’s prices). Its row is marked Managed by another system. People who may change who sets price levels also see Why can’t I edit this?, which opens the level’s Who sets ‹level› dialog. A price at a level an ERP sets is read-only too, for the products linked to that ERP: it says “Comes from ‹ERP› · read 4 minutes ago” (no age while Read prices from the ERP is off), “Waiting for ‹ERP›‘s prices” until it has landed, and “‹ERP›‘s price could not be stored; it is tried again at the next read” if it failed. A product not linked to the ERP keeps an editable price. See Prices from your ERP. If a price became read-only while you were editing, saving keeps your other changes and says “These prices were not saved.” and “These prices come from another system and were not changed: ‹levels›.” When someone else saved the product meanwhile, the conflict dialog says “Your change to ‹level› cannot be kept: another system sets these prices now.” Duplicate product copies only the prices Omnilinker may write: “Prices managed by another system were not copied: ‹levels›”. A bundle price that follows its components is calculated only on levels Omnilinker owns.

​

Selling price history

Selling price history, below Cost history on Pricing, lists every change of the product’s selling prices, newest first: When, Level, Price (net / gross) and Set by. Set by names the kind of writer (Person, Repricer, Another system), who it was and how the price was written, for example Person · Anna Nowak · Bulk edit. Choose a level in Price level to see only its prices. A price level deleted since shows as Deleted price level. The history starts with this version: “No price changes recorded yet. The history starts with this version.” Each change is kept for 180 days. To change that, set Keep selling price history (days), from 30 to 3650, in the Catalog group of Administration > Settings. Older entries are deleted every night, but the latest change of each price is always kept, however old, so the history never goes empty for a price nobody changed in that time.

​

Edit the prices of many products

Select products in the list and click Edit fields. Under Price, choose a level and side, how it changes (set to, change by % or change by amount) and the value, then click Apply to ‹n› products.

• A level that another system manages is refused: “Prices at ‹level› are managed by another system, so a bulk edit can’t change them.”
• After the edit, Bulk edit result lists under Prices a rule may set again the prices you set that a repricer rule covers: “Written as you asked. These rules may set them again at their next run.” Each rule shows its prices and its next run, for example “In Repricer rule “Allegro min” · 3 prices · next run 14:00 proposes new prices”. Keep these prices… opens Keep my price for those products. One dialog takes a limited number of products: “Keeping applies to the first ‹n› products by SKU.”

A price import reports the same list; see Import prices.

​

Fields that come from your ERP

When a product is linked to a product in your ERP, some of its fields can come from there. You choose which on the connection’s product settings, with Edit product settings on its Warehouses and products tab: see Products from your ERP. Under a field that comes from the ERP, the product’s Details (or, for the purchase cost, Pricing) say “Comes from ‹ERP› — replaced when ‹ERP› changes it.” You can still edit the field. Your value stays until the ERP changes that field, and then the ERP’s value replaces it. On Pricing the note names the field: “Purchase cost: comes from ‹ERP› — replaced when ‹ERP› changes it.” While you edit, the notes under Dimensions and Weight name their field the same way. Above the Details you also see where the product stands in the ERP: Linked to ‹ERP›, Linked to ‹ERP› · inactive in ‹ERP› or Linked to ‹ERP› · missing in ‹ERP›. If the ERP’s details cannot be read, the product shows no markers, and you can still edit it. Images can come from the ERP too; see Images from your ERP.

​

Who manages SKUs

The SKU is the one field Omnilinker treats more strictly. By default your team edits SKUs and deletes products in Catalog. A connection to your ERP can instead manage them: the ERP then sets the SKU of every product linked to it. Above the product list, Who manages SKUs shows who does. The line appears only when it has something to say or do:

• Change owner opens the window where the manager is chosen. It needs the Choose where product SKUs and fields come from permission, and it appears only when there is another manager to choose.
• Set up products from ‹ERP› opens the connection’s card, where you decide which fields the ERP fills.

When the ERP manages SKUs, a product linked to it behaves like this:

• Its SKU is read-only. A lock icon beside the SKU explains it: “This SKU comes from ‹ERP›. Change it there.”
• Delete is disabled on the product and in the list’s row menu: “‹ERP› manages this product: its SKU is set there and it can’t be deleted in Omnilinker.” A bulk delete that includes such a product deletes nothing and names the first one: “‹sku› is managed in the ERP, so it can’t be deleted in Omnilinker.” A product that is not linked can still be deleted.
• An import row whose GTIN matches such a product but gives it another SKU is refused: “Row ‹n›: GTIN ‹gtin› belongs to ‹sku›, which is managed in the ERP, so its SKU can’t be changed to ‹sku›. Use SKU ‹sku› in this row, or change the SKU in the ERP.”
• You can still create a new product. Once it is linked to the ERP, its SKU comes from there.

If the ERP stops managing SKUs, or a linked product disappears from the ERP, the SKU is yours again.

​

Send prices to your ERP

With the Send prices to ERP permission and an ERP connection, you can send a product’s saved prices to the ERP price levels they are mapped to. Open the product’s actions menu and choose ERP prices, or select products on the list and choose Send to ERP. Only the prices of a level Omnilinker sets are sent (see Who sets a level’s prices). A level can also be sent automatically once someone switches that on for it on the ERP connection; the dialog then says Sent automatically when the price changes or Waiting to be sent automatically, and Send now sends the price at once. While the level is being handed to the ERP from Omnilinker’s prices, it says Sent automatically until ‹connection› takes this level over. See Send prices automatically. For a level the ERP sets, the dialog says Received from ‹ERP›, does not send it and shows “In ‹ERP›: net … · gross …” with when it was read. See Prices to your ERP and Prices from your ERP.

​

Related pages