Skip to content
Bulutegra Help center Troubleshooting

Common problems

A short fix list for rejected credentials, listings rejected by a marketplace, stock that won't update and stuck orders.

The channel rejects your credentials (401)

Symptom: under Settings → API Credentials (Ayarlar → API Kimlikleri), the channel card says credentials rejected (kimlik reddedildi) and shows since when. Orders can't be read from that channel, and stock and prices can't be sent.

Common causes: the key was renewed or expired in the channel panel, the password changed, the authorisation was withdrawn, or a space slipped in at the start or end while copying.

Fix:

  1. Generate a new key in the channel's seller panel.
  2. On the channel card, press Edit credentials ›, paste the new value and press Save.
  3. For Etsy and eBay, authorise again with Open authorisation link.

The change applies immediately; check that the card goes back to "connected".

A listing was rejected by the marketplace

  1. Open the Products → Quality (Ürünler → Kalite) tab. This screen answers one question: which marketplace listings are broken, and what do you need to do? Each finding has a What to do (Ne yapmalı) note.
  2. Read the rejection message. The most common causes: required category fields are missing, the barcode clashes with another product, the brand isn't registered on the channel, an image breaks the rules, or the variant structure is wrong.
  3. Category, brand, colour and size equivalents live on the Marketplace mappings (Pazar yeri eşlemeleri) page; for rows "awaiting approval", set an equivalent with Select (Seç).
  4. Fix the gap and send again. The send first shows a preview on the Operations (İşlemler) page, and nothing is written until you approve.

Stock isn't updating

Check in this order:

  1. Matching: look at the Code matching and Data integrity rows in the Pending jobs table on the channel page.
  2. Channel switch: on Channels → Channel Switches (Kanallar → Kanal Anahtarları), is that channel's stock + price switch on?
  3. Ownership: if the product is flagged "External system" or "Nobody" on that channel, Bulutegra leaves it alone.
  4. Stock limit: if a cap is set for that channel, no more than that many units are sent.
  5. Credentials: does the channel card say credentials rejected?
  6. Mass-reset brake: is there an alert under Notifications saying a send was stopped?

Products that are out of stock on your side but still on sale on a channel are listed under Channel stock audit on the Notifications → Alerts tab.

The price won't change

It may be the price brake, the profit floor or a marketplace campaign lock. The full checklist is in the Stock and price sync article.

An order is stuck

  1. Find the order in the Orders → Not transferred (Siparişler → Aktarılmamış) view and read the reason in the Transfer column.
  2. In the Orders → Transfer (Aktarım) view, press retry transfer on the failed row.
  3. If the reason mentions a code that isn't defined in the ERP, create the code in your ERP first.
  4. If the order's status is Not updated for 3 days, check the order in the channel's own panel.
  5. If the alerts show a quantity or amount mismatch, a cancellation or partial return may not have been processed in the ERP yet.

Still not solved?

Ask the Assistant (Asistan) or write to destek@bulutegra.com. Include the channel, the order number and the message you see. Never send a password or API key.

Didn’t find your answer?

Write to our team — we answer setup and usage questions in Turkish and English.