Quick answer: With most wholesale suppliers, ordering means one thing: log in and click. orosy's buyer portal gives you three, and they are not three services. The screen, an AI assistant connected over MCP (Model Context Protocol), and a direct API integration share one catalog, one cart and one business account. The screen fits a shop deciding quantities in front of the shelf, the assistant fits daily exploratory buying where the conditions change every time, and the API fits connecting your own storefront or inventory system. Production orders have come in through all three ways of ordering (as of 2026-09-29). Every route starts the same way: sign up as a business, pass review, then issue your own API key from the logged-in screen if you want the other two.
Key takeaways
- Sourcing conversations answer where to buy. What is left after you pick a supplier is how to order, and that repeats every week for as long as the relationship lasts.
- The three routes are entry points to one transaction, not three products. The catalog, the cart and the business account are shared, so an assistant can build a cart that you confirm on the screen.
- Keep manual ordering working from the screen first. A half-finished integration should never be able to stop your purchasing.
- An AI client can only connect if it supports MCP and lets you set an
Authorizationheader. Claude Code, for example. - While you wait for review, test mode lets you walk the whole path on screen, from search through to placing an order, with no supplier notified, nothing shipped and nothing charged.
Sourcing decides where you buy. Ordering is the work that is left
Almost everything written about buying from Japan is about selection: which marketplace, which importer, which trade show, whether to go direct to the maker. We have written that map ourselves in where to buy Japanese products wholesale online.
But the sourcing decision happens once. The ordering happens forever. Once a supplier is chosen, the friction that remains is mechanical: open a browser, search, read the order unit, compare two similar items, fill a cart, check the minimum order amount, confirm. Multiply that by a weekly cadence and it stops being a detail.
This is where the phrase "API integration" gets in the way. It sounds like a project with a budget and a kickoff meeting, so buyers file it under someday and keep clicking. In practice, ordering by hand and ordering through a wholesale API are not competing choices. They are two of three ways into the same transaction, and nothing stops you using both in the same week.
What follows is a decision guide to the three wholesale ordering methods: what each is good at, what it costs you to set up, which operations each suits, and how to start an integration in an order that does not leave you stuck.
The three ways to place a wholesale order, side by side
The clearest way to hold the three apart is to ask who operates the catalog. On the screen, a person does. Through an assistant, a person says what they want and the assistant does it. Through the API, your own program does.
| Route | What it is good at | What it costs you to set up | Who it suits |
|---|---|---|---|
| The portal screen | Searching, comparing, filling a cart, placing the order and pulling invoices, all by hand. You see every condition as you go. | Nothing beyond an approved business account and a browser. | A shop deciding quantities on the floor, in front of the shelf that needs filling. |
| An AI assistant over MCP | Describing what you want in words, having candidates assembled, and getting a cart built with the conditions read for you. It stops and shows the total; you place the order. | An MCP-capable AI client that lets you set an Authorization header, plus an API key you issue yourself. No code. |
Daily exploratory buying where the brief changes every time: a theme, a price band, a season. |
| A direct API integration | Pulling product data, operating the cart and placing orders from your own program, on your own schedule. | The same API key, plus someone who can write the calls: in-house, contracted, or an AI client writing code. | Connecting your own storefront or inventory system, where the same steps repeat without variation. |
Two things the table leaves out.
The assistant route has a real connection condition, and it is not a brand. A client can connect if it supports MCP (Model Context Protocol, a shared standard for connecting an AI client to an outside service) and if it lets you put the API key in a request header. Claude Code, for example, does both. Clients whose connection method does not allow that header cannot connect directly today. Check that one capability before you plan around a particular tool.
The API route does not require an engineering department. Writing the calls is a task, not a headcount: an outside contractor can do it, and so can an AI client that writes and runs code against the same key. A member of our overseas team who runs a Shopify B2B store wrote up what that looked like in field notes from a first run against the orosy API.
The assistant route in depth (what you need to connect, what the agent can and cannot do, and where it stops) is its own article: ordering Japanese wholesale with an AI assistant over MCP. Here we stay at the altitude of choosing.
Which route fits your operation
There is no best route, and the answer is not a function of company size. It falls out of two things: where the buying decision physically happens, and what capacity you have in the building.
| Your operation | Route to start with | Why |
|---|---|---|
| Brick-and-mortar retail, buying against gaps on the shelf | The screen | The trigger for the order is visual and immediate. A person standing in the aisle is faster than any integration. |
| An online store rotating its assortment, hunting for what is new | Assistant, plus the screen | The brief changes every time, so describing it in words is faster than rebuilding a filter set. |
| A storefront or inventory system you want the catalog to feed | The API | Product data pulls and repeat orders become steps in your own process rather than human work. |
| Several buyers sharing the work across categories | The screen, plus the API | People order from the screen; only the mechanical parts, such as pulling product data, move to code. |
| No developer capacity yet, and no plan to hire | The screen, then the assistant | You start trading immediately, and the assistant gives you most of the automation benefit without an implementation. |
Reading a Japanese price sheet is a separate skill from choosing a route, and it bites on all three: order units, pack quantities and the tax lines look unfamiliar the first time. We cover the vocabulary in Japanese wholesale terms explained, and the arithmetic of turning a wholesale price into a per-unit cost at your own door in the landed cost model for Japanese products.
What the three routes share, and why it matters more than the differences
It is not that there are three ways in. It is what sits behind all three.
| Shared | What it means in practice |
|---|---|
| One catalog | A product you find on the screen is the same product your code or your assistant can retrieve. Your assortment does not depend on which door you came through. |
| One cart | You can switch mid-task: have an assistant assemble the cart, then open the screen to check it and confirm. Nothing is rebuilt. |
| One business account | Adding a route needs no new registration and no second review. Orders from any route land in the same order history. |
| One set of wholesale conditions | Order units and minimum order amounts per shipping origin apply identically whichever route places the order. No route gets different terms. |
The value of this shows up by contrast. Where every supplier has its own login, each new one means re-entering your company details, learning another screen, and reconciling another invoice at month end. Twelve suppliers is twelve of everything. The point of one account across many suppliers is that the count stops growing.
How to start a wholesale API integration without stopping your buying
The sequence matters more than the code. Here is the order that leaves you safe at every step.
- Sign up and get manual ordering working. Registration takes your company name, the URL of your business website, and a description of your business. The website URL is mandatory by design and is what review is based on. Registering is free and takes no credit card.
- Use the wait to learn the flow in test mode. While you wait for review you can run the whole path from search to placing an order on the screen. Suppliers are not notified, nothing is shipped and nothing is charged. This is where you learn what the order form asks for and what the conditions look like, before any of it reaches a real supplier.
- Place your first order from the screen. Once approved, order by hand once, checking the conditions with your own eyes: the order unit, the minimum order amount, the shipping fee. This usually takes about 15 minutes.
- Issue your API key. After approval you issue the key yourself from the logged-in screen. No development knowledge and no support ticket. A test key is one of the options, so your first calls can run without a real charge or real inventory movement.
- Connect an AI client, or write your first call. Set the key as a header in an MCP-capable client, or point your own code at the product search. The setup steps for the AI route are in the "Use with AI" guide after you log in.
- Move one repeating task at a time into your own system. Product data pulls first, because they are the highest-volume and least risky. Ordering last.
Run it in this order and manual ordering keeps working throughout. That is the reason for the sequence: an integration in progress is a normal state to be in for weeks, and purchasing cannot depend on it finishing. It also heads off an avoidable wasted week: building against a wholesale API integration for days, then finding that the order being automated sits below a minimum order amount.
The three routes on orosy's buyer portal
orosy's buyer portal is a wholesale platform where multiple Japanese suppliers and roughly 200,000 products sit behind one screen and one cart, from search through ordering to tax invoices you can file. That figure is the catalog inside Japan; the range available for shipping to your country depends on the destination, as the shipping section below sets out. orosy also runs a wholesale marketplace in Japan with 5,000+ brands, and those brands join this catalog over time. Registration and use are free; what you pay for is the goods and the shipping. There is no setup fee, no monthly fee, and no credit card needed to register.
It is review-based. Registration requires the URL of your business website, and review uses 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.
Test mode covers the wait. On the portal screen you can go from search through to placing an order, with no supplier notified, nothing shipped and nothing charged. After approval, the live catalog with wholesale prices opens.
You issue the API key yourself, from the logged-in screen, after approval. The same key serves both the coded route and an MCP-capable AI client.
The assistant is required to stop before ordering. It searches, compares and builds the cart, then shows you the tax-inclusive total and waits. A person does the final check and places the order. Catalog search runs against Japanese product data, which is one practical reason buyers outside Japan reach for the assistant route: the assistant reads the Japanese product data for you.
Wholesale conditions are the same from every route. Each product has an order unit. 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. Meet those and you can order in small quantities. When something is out of stock, you are billed only for what actually arrives.
You can list before you hold stock. 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. Wholesale conditions still apply to that order: you cannot go below the order unit or under a delivery group's minimum order amount, and permission to use product images and copy varies by product rather than being granted across the board.
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. The range of the catalog available for shipping differs by destination country: for shipping to the US it is stationery, over 60,000 products. Setting your destination shows only the products that can ship there.
What the numbers look like so far
As of 2026-09-28, over 476 businesses had signed up, over 307 had passed review, and over 48 had issued an API key. Those are stages of one funnel rather than counts per route: the same key serves both an MCP-capable AI client and a coded integration, and a single business can use more than one of the three. Production orders have come in through all three ways of ordering: the portal screen, an AI assistant over MCP, and a direct API integration (as of 2026-09-29).
That matters for the decision in front of you, because it contradicts the assumption that the coded routes take months to reach. One home-and-garden online retailer in Germany went from signing up to a confirmed order in four days, review and API setup counted in, with the buyer confirming on the screen at the end. The AI-assistant route in detail covers the same case and what each step of connecting involves. The practical reading: when you plan an API or AI route, plan against calendar time like that rather than against the 15-minute flow, which describes a first order once your account is already approved.
FAQ
What do I need to order from my own system through a supplier's API?
Three things. First, the supplier has to publish an ordering API at all. Second, you need to be able to get your own credentials for it, which on orosy's buyer portal means passing business review and then issuing an API key yourself from the logged-in screen. Third, you need someone who can write the calls: an in-house developer, an outside contractor, or an AI client that writes the code for you. Signing up requires the URL of your business website, so have that ready before anything else.
How do I get an API key — do I need an engineer?
On orosy's buyer portal you issue the key yourself from the logged-in screen once your account has passed review. Issuing it takes no development knowledge; it is a screen you click, not a support request or a contract negotiation. The same key works two ways: your own program can call the API with it, and an MCP-capable AI client can connect with it. So a buyer with no developer at all can still put an API key to work through the AI route, and add a coded integration later without changing keys or accounts.
If I use all three routes, do I end up with separate accounts or separate orders?
No. The three are entry points to the same transaction, not three services. On orosy's buyer portal they share one catalog, one cart and one business account, which is what makes combinations work: you can have an assistant assemble a cart and then open the screen to check it and confirm the order. Adding a route later needs no new registration and no second review. Wholesale conditions are also identical whichever route you order from.
Can I try the ordering flow before my account is approved?
Yes. orosy's buyer portal has a test mode that lets you run the whole path from search to placing an order on the screen while you wait for review. Actions in test mode do not notify suppliers, and nothing is shipped and nothing is charged. It is there so you can see what ordering actually asks of you before a real supplier is involved. API keys are issued after approval, so rehearsing a coded integration comes after that step, and live orders start then too.
Can a business outside Japan use all three routes?
Yes. The routes do not change with your location, and you pick the destination country when you order. orosy arranges international shipping to your country. You do not need a forwarder or a receiving point in Japan. The range of the catalog available for shipping differs by destination country, and setting your destination shows only the products that can ship there. 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.