Quick answer: Ordering Japanese wholesale from an AI assistant means you connect your own AI client to a wholesale catalog over MCP, a connection standard, and then work in plain language: search, compare order units and minimums, build a cart, and check what is in it. The agent reads the live catalog rather than answering from training data, so the products, wholesale prices and stock it reports are real. You need three things to start: a business account that has passed review, an API key you issue yourself, and an AI client that supports MCP and lets you set an Authorization header. The one thing the agent cannot do is commit you. It has to fetch the tax-inclusive total and put it in front of you, and the order goes through after you agree. As of 2026-09-29, production orders have come in through all three ways of ordering: the portal screen, an AI assistant over MCP, and a direct API integration.
Key takeaways
- Asking a general chatbot "who sells Japanese stationery wholesale" and connecting an AI client to a catalog are two different activities. The first answers from training data; the second reads the live catalog, with current wholesale prices, stock and order units.
- Three things get you connected: a reviewed business account, an API key you issue yourself after approval, and an MCP-capable client that lets you set an Authorization header.
- The agent searches, reads product detail, browses shipping groups and categories, builds and edits the cart, and checks order status and your order history.
- The agent is required to show you the tax-inclusive total before it can place an order. Behind that, a moved wholesale price stops the order at the server with
409 PRICE_CHANGED, a required 3D Secure check hands you off to an authentication URL, and an account that has not passed review cannot order at all. - Wholesale trading conditions do not soften because an AI is doing the typing. Order units and minimum order amounts per shipping origin still apply, and goods arrive at your business address for you to pack and ship onward.
- The catalog available for shipping to the US is stationery (over 60,000 products). A buyer receiving inside Japan sees the full 200,000+ products.
Asking a chatbot is not the same as reading a live catalog
Type "who sells Japanese stationery wholesale" into a general chatbot and you get a reasonable-sounding answer assembled from its training data. It may name real companies. What it cannot tell you is what is buyable this morning, at what wholesale price, in what pack size, or whether the combination you have in mind clears a minimum order amount. A chatbot with no connection to the catalog is guessing at all of that.
Connecting is the other activity. You register the catalog with your AI client over MCP, and from then on the client calls the catalog's functions. Ask for candidates and the agent searches the real index, reporting back real products with their real conditions. Ask it to build a cart and it builds the actual cart your account owns.
| General chatbot conversation | AI client connected to the catalog | |
|---|---|---|
| What the model is reading | Training data | The live catalog |
| What comes back | Approaches, search tactics, company names | Real products with wholesale price, stock and order unit |
| What it can do | Explain only | Search, read detail, add to cart, check order status |
| Who confirms the order | Nobody; there is no order | The agent presents the total and stops; you confirm |
That last row is the one to hold onto. The agent's job pauses at "here is what this costs" until you say yes.
The three things you need, and how the connection works
Setup is short, and the sequence matters because each step depends on the one above it.
| What you need | What it is | Where people trip |
|---|---|---|
| A business account that has passed review | You register your company name, a business website URL and a short description of what you sell, then pass business review | The website URL is required. It can be your own store site or your online shop page |
| An API key | You issue it yourself in the portal after your account is approved | You cannot issue one before review finishes |
| An MCP-capable AI client | A client that supports MCP and lets you set an Authorization header so your key travels with the request |
A client can support MCP and still fail the second condition. Check both before configuring anything |
On review: 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. If the term order unit or minimum order amount is new to you, our guide to Japanese wholesale terms defines the vocabulary you will meet in the catalog.
Once you have a key, the connection itself is a URL plus one header. Any Streamable HTTP client can connect with those two values, and most MCP clients read a configuration block shaped like this:
{
"mcpServers": {
"orosy": {
"type": "http",
"url": "https://<endpoint>/mcp",
"headers": { "Authorization": "Bearer orosy_..." }
}
}
}
Clients with their own command line skip the file. Claude Code, for example, registers the server in one command and then reports the connection status and the tool list back, so you can see the catalog is reachable. Read the exact endpoint and the current command off the "Use with AI" guide after you log in.
Connect from an MCP-capable AI client that lets you set an Authorization header — Claude Code, for example. Clients whose connection method does not meet both conditions cannot connect directly today. Some popular connector features assume a different authentication flow entirely, and configuration does not get around that.
What the agent can do, and what it cannot do on its own
These are the functions the agent can call. Read the list as the shape of the work you can hand over, not as commands to memorize: you describe what you want in plain language and the agent picks the calls.
| Function | What it does |
|---|---|
| Product search | Searches every supplier's products in one query. Use several words and you only get products matching all of them; the search covers product name, brand, model number and category. Paste an 8 to 13 digit JAN code (Japan's barcode number, the equivalent of a UPC) to match that product exactly, several at a time separated by commas |
| Product detail | Returns one product in full: every variation, the wholesale price, the list price, stock and images |
| Delivery groups and categories | Browses the delivery groups and the category tree. A delivery group is orosy's unit for products that ship together from the same source. Shipping fees, any free-shipping threshold and the minimum order amount are set per delivery group |
| Cart operations | Reads the cart, adds items, changes quantities and removes lines, and reports the tax-inclusive total |
| Order status | Checks where an order stands, and returns an authentication URL when a 3D Secure check is required |
| Order list | Lists your orders newest first, so the agent can answer "what did we buy from this brand last time" |
| Place order | Places the order from the cart, after it has shown you the tax-inclusive total and you have approved |
A worked request looks like this: "Search for A5 notebooks, show me three with the lowest wholesale price, and if one looks good add twelve to the cart and tell me the total." The agent searches, opens the detail on the candidates, adds the line, reads the cart back, and stops with the total in front of you. What the list does not change is the order of operations: the agent is required to show you the total before it calls the order function.
The interesting part of ordering through an AI is what stops a confident agent from buying the wrong twelve notebooks. Three mechanisms answer that. Two of them are enforced by the server. The first is a required step the agent must follow before it may call the order function.
The total has to reach you first. Before it can place an order, the agent is required to read the cart, get the tax-inclusive total, and present that total to you for approval. The agent searches, compares and builds the cart, then it stops and shows you the tax-inclusive total, and you place the order.
A moved price stops everything. Wholesale prices can change between the moment an item goes into a cart and the moment the order is confirmed. When that happens, the order halts with a 409 PRICE_CHANGED response instead of completing at the new figure. The agent cannot quietly buy at a higher price; you get to look at the new number first.
A card check cannot be delegated. 3D Secure is a challenge aimed at a person, and an AI cannot complete one. When a card check is required, the order status call returns an authentication URL and the agent hands you off to it. You finish the check; the agent waits.
What stays your work, and what does not change
Connecting an AI does not move the boundaries of the trade. It changes who does the reading and the arithmetic in the middle of it.
| What you can hand over | What stays with you |
|---|---|
| Pulling candidates from across several suppliers at once | Deciding what belongs on your shelf |
| Reading order units, minimum order amounts and shipping conditions against each other | The final confirmation and the order itself |
| Assembling combinations that actually clear those conditions | Receiving the goods and checking them in |
| Looking up what you ordered before, and when | Setting retail prices and merchandising |
| Answering "does this cart clear the minimum yet" | Confirming image and description permissions per product |
Three points tend to surprise people who expect an AI integration to be a different product rather than another way into the same one.
The trading conditions are the wholesale conditions. Each product has an order unit, and each delivery group can carry a minimum order amount. The agent can read those conditions and tell you a given combination falls short of a minimum, but it cannot relax the condition itself. If you buy in small quantities, the mechanics are the same as ordering through the portal screen, and our stationery sourcing guide works through what that means for one category.
Delivery is to your business address. Goods go to a store, warehouse or office, not to your customer. Listing before you hold stock works: you list first and order after a sale comes in. The goods are delivered to your business address, and you pack and ship them to your customer yourself. Budget for that handling; it does not disappear when an AI does the ordering.
Image and description permissions are per product. There is no blanket permission covering the catalog, so the conditions for using a product's photos and copy differ from product to product. Check before you publish a listing on your own storefront. That is a judgment call about rights, which is why it stays on the human side of the table even when everything upstream of it is automated.
Is anyone ordering this way yet?
We can share the totals, not a split by route. The counts, all as of 2026-09-28: over 476 businesses had signed up, over 307 had passed review, and over 48 had issued an API key. As of 2026-09-29, production orders have come in through all three ways of ordering, which is to say the portal screen, an AI assistant over MCP, and a direct API integration.
One timeline shows how fast the setup can go when nothing gets stuck. A home-and-garden online retailer in Germany signed up, was approved automatically, issued its own API key, connected an MCP client and pulled the catalog, then confirmed the order in the portal. Four days, start to finish, with the key issuing and the connecting done by the buyer and the order confirmed by a person on the portal screen.
Those four days and our "about 15 minutes to a first order" figure measure two different things. Fifteen minutes describes the product flow once your account is approved: search, cart, confirm. The four days are real elapsed time, including review and API setup. One is the flow; the other is the calendar.
For a hands-on account from our overseas team, one of them connected the API to their own Shopify B2B store and wrote up the first run, including a photo problem that took one sentence to fix.
Where orosy fits
orosy's buyer portal puts several suppliers behind one catalog and one cart. 5,000+ brands on orosy's Japanese marketplace are joining this catalog over time, and the catalog holds 200,000+ products for a buyer receiving inside Japan. 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.
For a buyer in the US, the scope question comes first. The catalog available for shipping to the US is stationery (over 60,000 products). Set your destination country and the catalog shows what can go there, which differs by country.
On the shipping itself: 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.
The screen, an AI client over MCP, and a direct API integration all read the same catalog and drive the same cart. Nothing forces you to pick one: one workable pattern is to explore and assemble with an agent, then open the cart on the screen for the final look before confirming. Which route suits your team depends on how your buying runs day to day, and our comparison of the three ways to order takes that question on directly. If you are still mapping the routes into Japanese supply at all, start with the five ways US buyers source Japanese products wholesale.
Registration and use are free. What you pay for is the goods and the shipping, with no set-up fee and no monthly fee, and no credit card at sign-up. Sign-up asks for your company name, a business website URL and what you sell, and it is a reviewed service, so the wholesale catalog opens once your account is approved.
FAQ
What do I need to connect an AI assistant to a wholesale catalog?
Three things. First, a business account that has passed review, because wholesale prices only open after that. Second, an API key, which you issue yourself once your account is approved. Third, an AI client that supports MCP and lets you set an Authorization header, so it can send your key with each request. Claude Code is one client that meets both conditions. The setup steps live in the "Use with AI" guide after you log in.
Can the assistant place an order without my approval?
No. Before it can place an order, the agent is required to fetch the cart and show you the tax-inclusive total, and the order goes through only after you agree. Two more stops sit behind that. If the wholesale price moved after an item went into the cart, the order halts with a 409 PRICE_CHANGED response rather than buying at the new price. And 3D Secure cannot be completed by an AI, so when a card check is required the agent hands you an authentication URL and waits for you.
What is MCP?
MCP stands for Model Context Protocol. It is a connection standard that lets an AI client call the functions of an outside service instead of answering from what it learned during training. Once you register a service, the client can use that service's tools: in the case of a wholesale catalog, product search, cart operations and order status. The practical difference is that the answers come from the live catalog, with real products, real wholesale prices and real order units.
Which AI clients can connect?
Not all of them. A client has to meet two conditions: it supports MCP, and it lets you set an Authorization header on the request so your API key travels with it. Claude Code is an example of a client that does both. Clients whose connection method does not meet both conditions cannot connect directly today, so check your intended client against those two conditions before you start.
Do I still have to pass business review if I order through an AI assistant?
Yes. The catalog with wholesale prices opens after review, and that is the same whether you use the portal screen, an AI assistant or a direct API integration. Sign-up asks for your company name, a business website URL and a short description of what you sell, and the URL is required. 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. You cannot issue an API key before review finishes.