Quick answer: A home-and-garden online retailer in Germany signed up on orosy's buyer portal late one evening, had their business verified automatically about 20 minutes later, issued their own API key six minutes into their next visit, connected an MCP-capable AI client, pulled the catalog visible for delivery to Germany with a program run against the API, ran a one-item dry run in the cart the next day, and placed a real wholesale order four days after signing up. A person placed that order on the portal screen, after editing the cart by hand. One scope note before you read on: the catalog that can ship to the US is stationery, over 60,000 products as of 2026-10-05, while Germany sees adult apparel and kitchen & dining on top of stationery.
Key takeaways
- Four days is real elapsed time from sign-up to a placed order, with business review and API setup inside it. It is not the same figure as the roughly 15 minutes a first order takes once an account is already approved.
- Verification completed automatically in about 20 minutes here, because the email domain used at sign-up matched the business website on the form.
- The division of work held all the way through: exploration, catalog retrieval and cart assembly ran on an AI client and on code calling the API, and the order was placed by a person on the screen after a hand edit.
- No credit card is needed to sign up. A card is needed at the order step, and that is exactly where this buyer's first attempt stopped.
- What you can buy depends on your destination country: stationery for the US (over 60,000 products) and over 100,000 products for delivery to Germany, both measured on 2026-10-05.
Scope first: what a buyer in your country can buy today
This story happens in Germany, and Germany is in the EU. That matters for the assortment, because the range of the catalog that can ship to you is set per destination country rather than globally.
| Destination | What the catalog covers | Products (measured 2026-10-05) |
|---|---|---|
| United States | Stationery | over 60,000 for delivery to the US |
| Germany, and the rest of the EU, the UK, Canada, Australia and New Zealand | Stationery, adult apparel, kitchen & dining | over 100,000 for delivery to Germany |
| Any other destination | Stationery | over 60,000 |
| Receiving at a business address inside Japan | The whole catalog | 200,000+ products |
So the retailer in this record was shopping a wider assortment than a buyer in the US sees today. Setting your destination country shows only the products that can ship there, and liquids, sprays and children's clothing do not go overseas at all.
If you are reading this from the US, read the four days as a record of the process, which does not change with your location, and read the assortment as stationery. Our guide to Japanese stationery wholesale covers that category on its own terms. If you are in the UK or the EU, the kitchen and tableware side of what this buyer could see is covered in Japanese kitchenware wholesale for the UK and EU.
What the four days actually looked like
Most of what gets written about sourcing from Japan is written from the outside, in months. Find an agent, fly to a trade show, open an account, wait for a sample, wait for a price. The honest version of that timeline is long, and we have no interest in pretending otherwise.
What we can do is report one thing that the outside view cannot: our own record of an account that started from nothing and reached a placed order, with timestamps. This is a single account, so treat it as proof that it can happen rather than as an average. One case is still worth something where the assumption under test is "this takes months."
Two numbers get confused in conversations about this, so it is worth separating them before the walkthrough.
About 15 minutes is how long a first order takes once your account is approved: search, read the order unit, fill a cart, confirm. It describes the flow.
Four days is what this retailer's calendar actually looked like, from the moment it filled in the sign-up form to the moment an order existed. Verification, issuing an API key, pulling a catalog, a dry run and a pause are all inside that number. It describes the project.
When you plan a sourcing trial, plan against the second one. The first will mislead you in the optimistic direction, and the months-long folklore will mislead you in the other.
All times are the retailer's own activity, read off our logs, in Japan time.
| When | What happened | Where it happened |
|---|---|---|
| Late evening, day one | Signed up: company name, business website URL, a description of what they sell. No card. | Portal |
| About 20 minutes later | Business verification completed automatically | No human step |
| About 45 minutes after sign-up | Set the destination country and looked at the cart's reference figure for international shipping | Portal |
| Six minutes later | Issued their own API key, then connected over MCP within about 20 seconds | Portal, then an AI client |
| Over the next four and a half hours | Pulled product detail for the catalog visible for delivery to Germany, over 100,000 products, with a program run against the API | A program against the API |
| The following day | Put a single product in the cart and checked whether it could ship to Germany and what the shipping reference figure looked like | Portal |
| Four days in, morning | Added dozens of line items to the cart over the API, about one per second | A program against the API |
| Five minutes later | Opened the portal, removed three lines by hand, re-checked the shipping reference figure | Portal |
| Minutes after that | First attempt to place the order stopped: no payment card on file | Portal |
| About three minutes later | Added a card and placed the order | Portal |
Night one: a form, then nothing to do. Sign-up asked for three things, and the business website URL is the one that carries weight, because verification is based on it. The email address used at sign-up was on that domain, so the account cleared automatically about 20 minutes later. Nobody at orosy touched it. This is the fast path by design, and it is worth knowing before you choose which address to register with.
Within the hour: the destination, then a key. The retailer came back about 45 minutes after signing up and did the sensible thing first, which was to find out whether the economics could work at all: set the destination country, look at the cart, read the reference figure for international shipping. Six minutes into that visit they issued their own API key from the logged-in screen. The connection to an MCP-capable AI client followed within about 20 seconds, and the first searches were exploratory, a single category word tried against two destination countries.
Six minutes is the detail we would ask a skeptic to sit with. There was no sales call, no integration ticket, no credential request by email. Issuing the key is a screen you click once your account is approved, not a support request.
The next four and a half hours: pulling the whole thing. Then something happened that a portal visitor cannot do: a program ran against the API and pulled product detail for the catalog visible for delivery to Germany, over 100,000 products, in about four and a half hours. One detail from the logs is worth keeping: those calls arrived from the AI client's own environment rather than from the buyer's network, so we cannot tell you who wrote the code, only that it ran. We want to be careful about how the rest of this reads too. Nothing requires a buyer to pull a catalog, and nothing about the first order depended on it. What it tells you is what this buyer wanted, which was the assortment in their own format, so they could sort and compare it the way they sort everything else.
The day after: a one-item dry run. The next activity in the portal was small and, to us, the most recognizable moment in the whole record: one product into the cart, a check that it could ship to Germany, a look at the shipping reference figure. That is a buyer testing the rails with the smallest thing they can before committing. It is also the step most integration guides skip.
The morning of the order: machine fills, person edits. Dozens of line items went into the cart over the API at about one per second. Five minutes later the buyer opened the portal, removed three lines by hand, and re-checked the shipping reference figure. The first attempt to place the order stopped because there was no payment card on file. A card went on, and the order was placed about three minutes after that.
Four days, sign-up to order.
Which route did what in this story
orosy's buyer portal has three ways in, and the thing worth noticing in this record is that the retailer used all three inside one purchase rather than choosing between them.
| Route | What it did in these four days |
|---|---|
| The portal screen | Sign-up, setting the destination country, the one-item dry run, the hand edit of the cart, adding a card, and placing the order |
| An MCP-capable AI client | The first exploratory searches, minutes after the API key was issued |
| A program against the API | Pulling product detail for the catalog visible for delivery to Germany, and later filling the cart |
They work together because the catalog, the cart and the business account are shared. A cart filled by a program is the same cart the screen opens, which is what makes "machine assembles, person decides" a workable pattern rather than a demo.
We want to describe that pattern as it happened, not as a feature. The MCP tooling is designed to put the tax-inclusive total in front of you before anything is placed. In this case the buyer went further than that by hand: they opened the screen, deleted three lines, looked at the shipping figure again, and placed the order themselves. The order was not placed by an AI.
We are not going to re-explain the routes here. If you are choosing between them, three ways to place a wholesale order is the decision guide. If the AI route is the part you are weighing, ordering Japanese wholesale from an AI assistant over MCP covers the connection conditions and what the agent can and cannot do.
What a buyer needs in place before signing up
Reading backwards from the record, here is what a buyer needs ready, and when each one bites.
| What you need | Why, and when it matters |
|---|---|
| The URL of your business website | Required on the sign-up form and used for verification. If your sign-up email is on that domain, verification can complete with no human step |
| A business delivery address | Goods go to a store, warehouse or office. Direct delivery to a consumer is not supported, so if you list before you hold stock, you pack and ship to your customer yourself |
| A credit card | Not needed to sign up. Needed at the order step, which is exactly where this buyer's first attempt stopped |
An MCP-capable AI client that lets you set an Authorization header |
Claude Code, for example. A client can support MCP and still not let you set that header, so check that before you plan around it |
| Someone who can write the calls, only if you want the coded route | In-house, contracted, or an AI client that writes the code. The portal route needs none of this |
One more thing that is easy to miss in a timeline: there is no contract step and no onboarding call anywhere in the four days. Registration and use are free, and what you pay for is the goods and the shipping. The per-order wholesale conditions, such as the order unit and the minimum order amount, are a separate matter and are set out in the last section.
What this record does not prove
We would rather name the limits than have a reader find them.
It is one account. Four days is what happened once, not a service level we are promising you. Verification was automatic here because of a domain match; where that match is absent, a person checks the site and the normal window is within 12 hours, which moves the calendar.
The catalog pull was this buyer's choice and not a step in the process. If you read the five hours as a prerequisite, you have read it wrong.
The destination mattered to the assortment, as the scope table says, and a US buyer running the identical process would have been working with stationery.
And our visibility ends where the logs end. This article stops at the moment the order was placed, because that is the last thing we can state as a fact about it.
Where orosy fits
orosy's buyer portal puts several Japanese suppliers behind one catalog and one cart, from search through ordering to tax invoices you can file. For a buyer receiving inside Japan the catalog holds 200,000+ products; orosy also runs a wholesale marketplace in Japan with 5,000+ brands, and those brands join this catalog over time. orosy handles the negotiation and the account opening with each supplier, so a cart drawing on several sources still produces one order and one invoice.
Registration and use are free. There is no set-up fee, no monthly fee and no credit card at sign-up. It is a reviewed service: sign-up asks for your company name, your business website URL and a short description of what you sell, and the wholesale catalog opens once your account is approved. Most accounts are approved within about 10 minutes if the sign-up email domain matches the business website or the email is listed on it; otherwise normally within 12 hours.
Payment is by credit card. You are billed when stock is confirmed, and you are not billed for items that turn out to be unavailable.
Wholesale conditions are the wholesale conditions, whichever route places the order. Each product has an order unit. A delivery group is orosy's unit for products that ship together from the same source, and shipping fees, any free-shipping threshold and the minimum order amount are set per delivery group. Meet those and you can order in small quantities.
Searching in English. You can search in English: an English search term is mapped to Japanese search-term candidates and run against the catalog. Two things come with that. Product names and descriptions come back in Japanese, because only the search term is mapped. And the mapping does not hit for every word, so when a term returns nothing, searching in Japanese is the fallback. Buyers outside Japan often hand that reading to an AI client for exactly this reason.
Shipping, stated plainly. orosy arranges international shipping to your country. You do not need a forwarder or a receiving point in Japan. Before you order, the cart shows a reference figure for international shipping, for your information only. The actual shipping cost is calculated later and billed to you, and it can differ from that figure. Customs clearance in your country, import duties, and taxes at import are your responsibility. They are not part of the cost billed by orosy. Delivery to a receiving point inside Japan also remains available. If the duty and clearance side is new to you, importing Japanese products: customs, duties and logistics walks through what sits on top of the price you see.
A note on the terms rather than a promise: for goods that arrive damaged, mis-shipped or short in quantity, contact us within 5 days of receipt and the terms of use provide for a replacement or a refund.
FAQ
How long did business verification take in this case?
About 20 minutes, with no human step. The retailer signed up late in the evening and the account was verified automatically because the email domain used at sign-up matched the business website given on the form. That is the normal shape of it: most accounts are approved within about 10 minutes if the sign-up email domain matches the business website or the email is listed on it; otherwise normally within 12 hours, after a person checks the site and emails you the result.
Who actually placed the order in this case?
A person, on the portal screen. The cart was assembled over the API, dozens of line items at about one per second, and five minutes later the buyer opened the portal, removed three lines by hand, re-checked the shipping reference figure, and placed the order themselves. The MCP tooling is designed to put the tax-inclusive total in front of you before anything is placed, and in this case the final check and the order both happened on screen.
Would a buyer without a programmer get the same four days?
The parts that took the time were not the coding. Sign-up, verification, setting a destination country, the cart and the order all happen on the portal screen and need no development work at all. What this buyer added was a program that pulled the whole catalog and filled the cart, which is optional. A buyer with no developer can reach a first order on the screen alone, and can still put an API key to work through an MCP-capable AI client later.
What do I need in place before I sign up?
The URL of your business website, because it is required on the sign-up form and is what verification is based on. A business delivery address, because goods go to a store, warehouse or office rather than to a consumer. And a credit card before you order, though not before you sign up. Registration is free and takes no card, which is why the card question surfaces at the order step instead.
Would the same route work for a buyer in the UK or the EU?
Yes, and the assortment is the same as the one in this story, because Germany is in the EU. For the UK, the EU, Canada, Australia and New Zealand, adult apparel and kitchen & dining products can ship in addition to stationery. For delivery to Germany that came to over 100,000 products, measured on 2026-10-05. For delivery to the US the catalog is stationery, over 60,000 products on the same date. Setting your destination country shows only the products that can ship there.
Can I search in English, or do I need Japanese?
You can search in English. An English search term is mapped to Japanese search-term candidates and run against the catalog. Two things to expect: product names and descriptions come back in Japanese, because only the search term is mapped; and the mapping does not hit for every word, so for a term that returns nothing, searching in Japanese is the fallback. This is one practical reason buyers outside Japan reach for an AI client, which reads the Japanese product data for them.