1. Contents
  2. Guides
  3. Troubleshooting
  4. Product does not appear in the shop

Product does not appear in the shop

A product exists in TRADElube, but it cannot be found in the online shop or on the marketplace. This page walks the transfer route in its own order: from the product through the channel mapping and the task to visibility in the target system. Every step ends with a finding, and the finding tells you where to continue. At the end you know which station it is stuck at, and in most cases you can fix it there yourself.

It assumes you know what a channel mapping and a task are. Both are covered in the concepts and are not repeated here.

Prerequisites

  • The product number or another search term for the product concerned.
  • The channel it is missing from.

Step by step

  1. Is the product in TRADElube? Open the list through the Products navigation entry and search for the product number in the Filter field. If the product is already missing here, the cause lies upstream of the shop: the import has not created it. Then check the same route on the import channel, from step 3 on, and for how the import is set up see importing products from a file.

  2. Does the product carry a row for the channel? Open the product through the Edit button and inside it the Channels section at the very bottom. For every channel the product takes part in there is a row with the mapping, the timestamps and the state.

Channels section of a product with one row per channel, the mapping and the timestamps of the last execution

The finding decides where to continue:

Finding Meaning Continue with
No row for the shop channel No execution has picked the product up yet Step 3
A row with an error message in place of the state The transfer of this product fails Step 4
A row with Created, Modified or Neutral TRADElube has transferred it, the product has arrived in the shop Step 6

The state column sits on the right. The list can be shifted sideways inside its box.

  1. Did the task run at all? Open the Tasks navigation entry. The columns Started At and Stopped At show the last execution. Two cases are frequent here, and neither is a fault: a new product only reaches the shop with the next execution, and a task whose Performance field is set to Manually only runs when somebody presses Execute. What the scheduling means in detail is covered under planning and starting tasks.

    If the task ran and the product still has no row, the execution did not take it along. Two places in the task decide that: a filter restricting the transfer scope (see restricting the transfer scope), and the Selection section of the transfer plan. If the New Item row is deselected there, the execution creates no new counterparts and skips every product without an existing mapping.

  2. What does the error message say? In the Channels section select the channel's row and open Show Traces, then the tab of the task. Or come from the other side: the Traces navigation entry shows all transfers, and the Filter field narrows them down to the product number. As soon as you select the row, the message appears above the list, with short message, plain text and note.

Traces filtered to the import task, with the selected failed row's message shown above the list

How such a message is structured and what the frequent ones mean is covered under understanding error messages. For this checklist the frame is what counts: the error applies to exactly this record, the task as a whole may well have succeeded, and the entry stays until the product is through. If the state carries the addition Skipped, TRADElube left the product out deliberately: a condition in the Selection section did not apply, or a counterpart was missing, the parent article of a variant for instance.

  1. After the fix: set it going again. The next execution picks a failed record up by itself. A manually started one does so immediately, without waiting out the pause that follows an error. What has already gone through and has not changed since, however, an execution does not transfer again. That is exactly what Restart on the selected trace row is for, and Restart All on the task for the whole stock.

  2. Arrived and still not visible? If the traces report Created or Modified, the target system has accepted the product. Then the cause lies in its visibility rules, not in the transfer: the product is inactive there, assigned to no category, not assigned to the sales channel, or it is a variant and appears only as a version of its parent article rather than as an entry of its own. What TRADElube sent is evidenced by the transferred content in the traces. What the system makes of it sits with the system. The limits and peculiarities of your system are on its own page under channels and tasks.

Checking the result

After the next execution, the product's Channels section shows a row for the channel with the state Created or Modified, and the product can be found in the shop. A Neutral here is a good sign too: it means both sides already match and there was nothing to do.

Frequent pitfalls

  • The traces open filtered. Of the five state filters, only Failed is ticked when you arrive in step 3. An almost empty list therefore does not mean nothing is running. Tick the remaining states to see what succeeded as well.
  • "Successful" and "no changes made" are not a contradiction. TRADElube only transfers what has changed. An execution over unchanged data establishes exactly that and is done. To transfer again regardless, use Restart or Restart All from step 5, not another execution.
  • An old value in Changes At is not a standstill. It says nothing has changed since. Whether a record is still being touched is answered by Executed At in the same list from step 3. The distinction is under traces.
  • Parent article and variant are two records, each with a transfer of its own. An error on the parent article drags follow-up errors onto the variants, because their counterpart is missing. Fix the parent article first, the one step 1 finds. The variants go through by themselves on the next execution.
  • Deleting a channel mapping is not a shortcut. With the mapping from step 2 the product loses its identity in the target system, and the next execution creates a second one there. If a transfer is to be forced, Restart from step 5 is the way: it leaves the mapping in place and only lifts the note that the record has been dealt with.

Further reading