Rakuten Ichiba Operations for Global Brands.

Rakuten Ichiba is not a marketplace by Western definition. It is an ecosystem of merchants, RMS (Rakuten Merchant Server), affiliate-style points economy and event-day commerce that behaves much closer to a portal than to Amazon. Foreign brands that try to operate Rakuten with an Amazon Seller Central playbook stall — we have watched it happen dozens of times.

The first reality: RMS is not Seller Central. Listings are HTML-rich item pages built page-by-page; mobile rendering rules differ from desktop; promotions live inside a layered calendar of store coupons, time-sales and super-sale events; and reviews flow through a separate "review automation" infrastructure that requires opt-in messaging within strict compliance windows. Almost none of this is documented in English at the depth required to actually operate.

The second reality: RPP (Rakuten Promotion Platform) is the dominant paid channel, and it decays. RPP keyword bids that worked yesterday will be outbid tomorrow when a competitor restructures. Bid management cannot be set-and-forget. We rebuild RPP keyword portfolios continuously — usually starting with hundreds of keywords, expanding to thousands once we map the long-tail.

The third reality: super-sale events (typically four to six per year) compress 2–3× of monthly volume into 72 hours. Day-of operations include hourly bid pacing, inventory rebalancing, in-cart price tests, and proactive customer-service capacity planning. Brands that "set and review later" miss the entire cycle.

The fourth reality: localization at the keyword level. Direct translation of an English PDP loses 60–80% of search demand because the queries Japanese shoppers type are categorically different — they reference brand-adjacent ingredients, color codes, JIS standards, body-shape vocabulary that simply does not exist in English copy. The fix is not translation; it is research-led re-authoring.

Daniel Wellington, Timex and AMOREPACIFIC sit on Rakuten because we ran it for them. Each engagement started with the same question — "can you actually log in and do this?" — and the answer was yes.

Operationally, we run your Rakuten storefront with a single account lead, a daily ops cadence, weekly reporting, and monthly QBRs. The team is in Tokyo, in your time zone for the day-of work that matters. We share a Slack channel; we share a Notion workspace; we attend your standups when needed.

We don't bill for decks. We don't bill per SKU. We bill a monthly retainer scoped to your channel mix and SKU count, plus a performance fee tied to incremental GMV growth on Rakuten — so when Rakuten grows, we grow with you, and when Rakuten flatlines, we have a structural reason to fix it.