Appearance
A day in the life
This is one working day of Ana, who runs the eMAG and Fashion Days accounts in marketplace operations. She has the operator role. Nothing in her day is unusual: most days look like this, and most of the work is looking, not doing.
Her accounts: eMAG RO, eMAG BG, eMAG HU, Fashion Days RO (all Live) and Fashion Days BG (new, in Preview).
08:30 — The morning check
Ana signs in with her company Microsoft account (see Signing in and roles) and lands on the Overview. The Live pill at the top right is green. In the sidebar, only Fashion Days BG carries a tag, PREVIEW. She reads the page from top to bottom, as described in The daily check.
The five tiles:
| Tile | What it says | What Ana makes of it |
|---|---|---|
| Offers in sync | 98 % — "70,765 of 71,590 linked offers", in amber | Expected. Fashion Days BG is in Preview, and its 812 waiting offers count as not in sync until it goes Live |
| Waiting to send | 824 — "812 held: the account can't send" | Normal: the 812 held belong to Fashion Days BG, which is in Preview; the other 12 are the 08:22 reading's changes going out |
| Needs a fix | 1 — "0 failed · 1 rejected · 0 orphaned" | Worth a look |
| Orders to check | 0 — "No order needs a person" | Good |
| PIM data | 7 min ago — "Read … · every 15 min" | Green: the last reading was at 08:22 |
Needs your attention has three rows:
- "1 offer rejected by the marketplace on eMAG RO" (amber). Ana clicks View offers and lands on Offers, already filtered to the rejected offers of eMAG RO. She hovers over offer 204411's status: its Last problem is eMAG's campaign message. Campaign locks are retried every 6 hours, so she leaves it. (Why: Sending stock to the marketplace.)
- "Full PIM check failed" (amber). She clicks View runs and lands on Activity → Sync runs. The error reads "Refused to remove 5210 of 99012 catalog items (limit 5%)". The PIM had a problem at 02:17; Stock Sync refused to set 5,210 products to 0. She forwards the message to the technical team and the PIM team. Nothing was removed, so no offer was harmed. (Why: Reading the catalog from the PIM.)
- "Fashion Days BG is in Preview" (blue): "Going Live would send 812 stock updates. Check its offers first." That is this afternoon's job.
09:15 — "eMAG says we have 3, but the shop has none"
Customer service forwards a complaint: a customer ordered a coat on eMAG RO and the order was cancelled for lack of stock. Ana follows Find out why a stock number is wrong.
She presses Ctrl K and types the coat's barcode. One offer on eMAG RO; she opens it. Its side panel shows the status In sync and the stock path:
| PIM stock | Rules | Stock to publish | Sent | Marketplace shows |
|---|---|---|---|---|
| 0 / 0 | Eligible | 0 | 0 | 3 |
The History shows that at 07:07 the PIM dropped to 0 and Stock Sync sent 0, which eMAG accepted. Marketplace shows 3 is older: it is what the 04:41 import read, before the change. So Stock Sync did its job at 07:07. The order came in at 06:50, before the PIM knew the coat had sold in the shop. Ana tells customer service that the warehouse, not the marketplace, was late, and the next import will show 0.
10:40 — The PIM team fixes something
The PIM team writes: "We fixed 300 products whose stock was wrong since yesterday." The next reading is at 10:52. Ana does not want to wait, so she presses Read PIM now on the Overview. The message says "A PIM reading was requested. PIM data updates when it finishes, usually within a minute." A minute later Happening now shows the finished PIM reading, the PIM data tile reads 1 min ago, and Activity → Sync runs has the reading with "300 changed". (See Read the catalog again now.)
11:30 — An account is suspended
Without reloading anything, Ana sees a red row appear at the top of Needs your attention: "eMAG HU is suspended", with "eMAG offer/save answered 401: …" (401 is the marketplace's code for a wrong login), and a red SUSPENDED tag beside eMAG HU in the sidebar. An amber row says "Sending round failed for eMAG HU": the round that met the refusal.
Ana asks the colleague who manages the eMAG HU seller portal. Yes: they changed the API password this morning. Ana:
- Clicks Edit connection on the row. It opens eMAG HU's Settings tab at Connection (Account settings).
- Enters the new API password and clicks Save. The other fields stay as they are.
- Clicks Recover in the account's status banner and confirms.
The message: "eMAG HU is recovered; its offers are being imported and its waiting stock updates sent." Stock Sync imports the offers, recalculates them and sends the 45 updates that waited during the hour, all within a few minutes; the next sending round also clears the "Sending round failed" row. The whole episode is on eMAG HU's Activity tab, with her e-mail address. (See Bring back a suspended account and Account health and pausing.)
14:00 — Reviewing an account in Preview
Fashion Days BG was created on Monday and has been in Preview since. Its status banner says "Going Live would send 812 stock updates now."
Ana checks, following Go from Preview to Live:
- On the Summary tab: Not linked 179. She notes them for the listing team: those offers were listed with wrong ids and will never be synced until they are listed again.
- On the Offers tab she picks the Waiting view, opens the first row in the side panel and walks through ten offers with J. For each, Stock to publish matches the PIM's available stock, and differs from Marketplace shows, which is last month's manual upload.
- She picks Not eligible in the Eligible filter: none, because Fashion Days BG has No limit.
She sends the product owner the numbers and gets the go-ahead.
15:30 — Going Live
In Fashion Days BG's status banner, Ana presses Go Live. The dialog Go live with Fashion Days BG? repeats that 812 updates will be sent. She types Fashion Days BG exactly and presses Go live.
"Fashion Days BG is Live; its waiting stock updates are being sent." The status turns green Sending and the PREVIEW tag leaves the sidebar. A few seconds later a Sending round for Fashion Days BG with "812 published" appears in the feed, and the account's In sync climbs to about 100 % while she watches. (Why this is safe: Preview and Live.)
17:45 — Pausing for the evening stock count
The warehouse will count stock between 18:00 and 20:00, and the PIM's numbers will jump around. Ana pauses eMAG RO, the busiest account, so it does not publish half-counted numbers. She presses Pause in its header and confirms "Nothing is imported, recalculated or sent to the marketplace for eMAG RO until it is resumed."
eMAG RO now reads Paused, with an amber PAUSED tag in the sidebar. The Overview's tiles leave eMAG RO out while it is paused.
She hands over to the evening colleague: "Resume eMAG RO after 20:00, when the warehouse confirms the count." At 20:15 the colleague presses Resume in eMAG RO's banner: Stock Sync imports the offers, recalculates them and sends the final counted numbers in one go (these steps are requested together, so their order in the sync runs can vary). (See Pause and resume an account.)
What Ana did not have to do
- Send any stock by hand. 71,000 offers followed the PIM all day.
- Reload a page: everything she watched changed on screen as it happened.
- Retry anything after the short eMAG slowdown at 12:10: the offers waited a minute and went out on their own.
- Worry about the 179 not-linked offers on Fashion Days BG: Stock Sync never touches them.
- Clean up old history: that happens at 03:53 every night.
More stories like these: Worked examples.