Four Rejections — What I Checked Before the Service Provider
A salesperson sees a seller in a Telegram group mention four product rejections and a promo next week. Instead of jumping to "this is an opportunity," he opens Merchant Center, copies down three numbers, and sets a review date for the facts to surface.
I leaned back into the sofa and scrolled Telegram. When a message popped up in the group, I unconsciously brought the phone half an inch closer.
The conversation below is an illustrative composite, not from any real group or seller. It is here only to show what I looked up and what I thought after reading it.
Illustrative/composite scene — cross-border seller operations group (Nov 6, 15:42)
Operations Chen: Li, SKU-2217 on Germany got rejected for the fourth time. Still “missing unique identifier.” The same item on UK passed last month. The feed provider has not responded today. Black Friday deals on Monday already locked inventory, and this one is stuck.
My first reaction: this seller has a feed problem. My second: I know people who run feed management services. Both reactions were too early. I locked the phone screen and did something else — not reply, not forward — I opened the Merchant Center status page.
Three Numbers, Copied Off the Status Page
Google Merchant Center — GMC, the backend where every seller using Google Shopping sees their product listings — has a Products page. Each row is one product record showing whether it is approved or disapproved in each market.
I pulled up SKU-2217 for Germany and copied down three numbers.
Number one: 4.
Rejection count is easy to overlook. If a field was simply missing at submission, one fix clears it. A second rejection means the fix was probably aimed in the wrong direction. By the third and fourth — with the same rejection reason unchanged each time — the submitter has been trying the same approach repeatedly without finding the actual cause. As of the moment I read the status page, the current maintainer’s solution for this SKU was not working.
There was one question I could not skip: what if the seller’s own data was incomplete? If the supplier never provided a GTIN required for the German market, the feed provider simply has nothing to fill in. I could not confirm this from the status page. I filed it as “to verify” in my head.
Number two: 4 days.
I looked at the submission dates on the status page. Each resubmission gap was roughly four days. That alone does not mean something is wrong. Some feed operations teams work on a three-to-four-day review cycle — submit, wait for results, revise, repeat. The problem was not the four-day interval itself. It was that all four intervals were nearly identical. Every round followed the same loop: receive rejection, edit, submit, wait, receive rejection again. Not one round showed extra time spent investigating the root cause. The rhythm suggested a possibility: whoever maintains this feed might be patching the surface rather than stepping back to re-examine the data source.
Of course, that is only one possibility. Another is that the seller’s internal review process held up each change for three days before approving the resubmission. In that case, the four-day gap is not the feed provider’s fault.
Number three: 2 days.
November 6 was a Wednesday. Monday, November 11, was when Black Friday offers go live with inventory already locked. Google product review typically takes one to three business days after a modified submission. For this SKU to make it by November 11, the final submission had to clear review no later than November 7 or 8. Counting from the moment I read the message, that was at most two business days.
On their own, each number is just information. Together, they formed a timeline with weight.
The Space Between the Three Numbers
Not every group message is worth following up. I have seen plenty of “another error here” complaints in groups, and most are resolved within hours with a “fixed it, was a typo” follow-up. Three messages later, the original complaint becomes background noise.
But this time, there was a gap I recognized between the three numbers. The rejection count (4) and the resubmission gap (4 days) showed a repeating problem. It was the two-day deadline that pulled this message out of my “wait and see” list.
I use a purely illustrative timeline below to show the calculation I ran through at the time. The dates and numbers exist only to demonstrate the logic — they do not represent any real seller’s data.
Illustrative Merchant Center review record
| Date | Event | Note |
|---|---|---|
| Oct 20 | First Germany submission | Rejected, “missing unique identifier” |
| Oct 24 | First revision submitted | Rejected, same reason |
| Oct 28 | Second revision submitted | Rejected, same reason |
| Nov 2 | Third revision submitted | Rejected, same reason |
| Nov 6, 15:42 | Operations Chen posts in group | Issue unresolved |
| Nov 11 | Black Friday offers go live | Hard deadline |
Two business days remained until November 11. If the current provider could find the fix and get it through review on November 7 or 8, the SKU would make the promo. If not, the next traffic window for this SKU would likely be the Christmas promo cycle, roughly five weeks away. Five weeks. If the seller is on a monthly contract, that crosses a renewal point.
These contract-related inferences assume the seller pays month to month. If the contract is quarterly or annual, the renewal logic is completely different. I could not confirm this from the status page or the group message. It would need to be checked in a later conversation.
Log It, Do Not Chase It
After I read the three numbers and that timeline, I did not DM Operations Chen. I did not post in the group either. I opened my lead sheet and wrote a record:
- Rejection count: 4, same reason, unresolved as of Nov 6.
- Resubmission gap: ~4 days per round, regular rhythm but root cause not addressed.
- Hard deadline: Nov 11, two business days from message timestamp.
- Cross-market difference: UK approved, Germany rejected four times. Cause unconfirmed — could be the feed provider’s filling accuracy or upstream data gaps.
- To verify: (1) whether the seller has received a response from the feed provider and what it says; (2) contract term and renewal window; (3) whether the supplier provides product brand and GTIN data.
Then I wrote the logical link between the first two items in the lead note: “4 rejections + 4-day gaps = suggests the current maintainer has been trying the same direction without breaking through. Not a final conclusion. Could be upstream data missing rather than filling capability.”
That sentence contained no “I think” or “I believe.” Only the numbers on the status page and the most direct logical relationship between them.
Wait Until the 14th
I set a calendar reminder: review SKU-2217 Germany status on November 14.
Why the 14th? After Black Friday goes live on November 11, if the last submission cleared review on November 7 or 8, the status page would show “approved” by the 14th. If it still shows “disapproved,” it means the current provider has not resolved this SKU’s issue in nearly two months.
On the 14th, I opened the status page and took a look. What comes next — each person walks a different path. But until then, I trusted only those three numbers.
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
