1. Contents
  2. Guides
  3. Troubleshooting
  4. Price does not match

Price does not match

The shop shows a different price than TRADElube. Hardly any deviation rewards narrowing down as much as this one, because the price the shop shows is the price it sells at. The good news: a price can only come from four places, the price group, the net-gross calculation, the scale, and the transfer itself. This page checks the four in that order.

It assumes the price model from the concepts: several price groups per product, the choice between net and gross per price line, the tax rate on the product.

Prerequisites

  • The product number of the product concerned and the price you expect.
  • The channel the deviation shows up in.

Step by step

  1. Which price group does the price come from? In its Prices section a product carries one price per group, and the shop receives the group selected in the task's transfer plan. Open the task that transfers the prices, usually the product upload, and inside its Transfer Plan section the part holding the prices. A price that looks "wrong" in the shop is often the correct price of the other group: sales price expected, trade price transferred, or the other way round.

Prices section in the product upload's transfer plan, with the Retail price group as the source of the price/gross target field

  1. Net or gross? On the product every price line has two columns, Net Price and Gross Price. Exactly one is entered, the other is derived from the tax rate and shown in gray. The transfer plan says which of the two is handed over. So compare the shop with the transferred column, not with the one you are used to. Two special cases belong here:

    • If the product carries no tax rate, there is nothing to convert, and net and gross are the same number. A shop expecting gross prices and receiving the net value still shows the expected amount, until the first tax rate is set. The tax rate sits on the product, in the Prices section above the groups.
    • If the shop calculates with a tax as well, its configuration decides whether it reads the delivered value as net or gross. If it reads it the other way round than intended, the displayed price deviates by exactly the tax rate. That factor is the telltale: a deviation of 19 per cent is almost never a typo.

  2. Does a scale apply? Within a price group each quantity range can carry a line of its own. A shop asking for the price at quantity 25 gets the line from 25 on, not the first one. Check the group's lines on the product before suspecting the transfer.

  3. What went over the wire? Once the three places above check out, the traces settle the rest: on the product, in the Channels section, select the channel's row, open Show Traces, then the task's tab. The kept content names the amount handed over, and that establishes whether the shop received what TRADElube sent, or whether the number was wrong before. The worked route for exactly this case, including the cross-check on the delivering channel, is under traces in the section "A price that is wrong".

  4. Since when? A price change only reaches the shop with the next execution of the task carrying the prices, and that one runs at a more leisurely pace than a stock task. Changes At in the traces says when the price was last actually transferred. The comparison of two states shows the transfer in which it changed.

Checking the result

After the correction and the next execution the transfer shows Modified, and the shop displays the amount of the transferred column. With a scale, check with the quantity the deviation was noticed at.

Frequent pitfalls

  • The name of a price group says nothing about its role. Name and type are two separate entries. Several groups may share a type. Which group the shop receives, which is what step 1 asks, is decided by the transfer plan alone, not by the name.
  • Falling for the gray number when comparing. In the comparison from step 2, gray is the derived value, black the entered one. Depending on the transfer plan, one side or the other is transferred. If you compare shop and TRADElube, put the same side next to each other.
  • TRADElube carries no currency. A price is a number, and all prices of a client are held in the same currency. If the target system requires a currency, it comes from the transfer plan as a fixed value. No "conversion" happens anywhere, not even in the transfer from step 4.
  • A period only takes effect on the special-offer price. The columns Valid From and Valid To exist only on groups of type Special-Offer Price. An expired special-offer price is therefore a normal reason for the shop showing the regular price again, and step 5 finds it through the date.

Further reading