Describing wholesale and online-store payments in one inquiry
Describe the public checkout and the wholesale or invoiced workflow as two channels, even when one legal entity, one brand, and one website operate both. WooCommerce usually creates an order when a customer completes checkout, and an administrator can also add an order in the dashboard. WooCommerce also documents sharing an invoice so an order can be paid. If a wholesale payment is a Stripe Invoice, Stripe describes an invoice as a collection from a specific customer, which is different from a payment link anyone can open. Calling a channel wholesale does not establish that a provider will process it. You can write how each channel creates an order, who places it in your records, and which system holds the payment. The provider decides whether it will accept that mix. Leave ticket size blank unless you calculate it from orders that have already been paid. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner of a research-use-only peptide business that takes both public-checkout orders and wholesale or invoiced orders.
Updated 2026-09-21
The channel is how the order is created and paid
Two orders on the same website can still be different workflows. One is created when a customer completes the public checkout. Another is created by a person in the store admin, or sent as an invoice to a named buyer. WooCommerce's order documentation says both the checkout path and the manual path exist, and that orders can be paid in more than one way, including an invoice shared with the customer. The inquiry should say which path is live.
Do not describe the public checkout as a wholesale account, and do not describe a wholesale invoice as an order that went through the public checkout. A provider reading the site and the processing records will see the method that was actually used. This page is about those workflows inside one business. It is not the map of separate brands and domains.
Name the payment record each channel produces
A checkout order and an invoice can land in different systems. Stripe's invoicing documentation says an invoice collects a one-time or recurring payment from a specific customer, and that the invoice cannot be reused for a different customer. The same Stripe page says a Payment Link is for anyone who has the link. Use those descriptions only if the channel actually uses that Stripe product. If it does not, name the ledger, bank transfer, or other record you use, and do not force the channel into a Stripe product you have not enabled.
The store order status is still a store fact. WooCommerce's Processing status means the store recorded payment as received. It does not identify which channel created the order. Say the channel in the inquiry even when the status word is the same.
Use paid orders for size, and keep forecasts out
If you have orders that were paid, you can summarize each channel from those records: how many, the range of amounts, and the method used. Calculate the channels separately. A single average that mixes a large invoice with a small checkout order describes neither channel. This page does not supply a typical amount. If a channel has no paid orders, write that it has none.
A forecast, a target account, or a buyer's stated intention is not processing history. You may say a channel is planned. You may not present the plan as volume the business has already processed. Who the buyer is, in your own records, is also a fact you can state. It is not an eligibility finding. Wholesale does not establish that a provider will accept the business, and a public checkout does not establish that either.
What you can explain, and what the provider still decides
You can explain which channels are live, how an order enters each one, who places it, how it is fulfilled, and where the payment record sits. You can say which of those facts you do not know yet. The provider decides whether it will process one channel, both, or neither, and what the price and reserves would be. Fulfillment differences belong in the description because they change the order. They do not, by themselves, answer the processing question.
Prism can help you organize this description for a processing conversation or a provider's question about the website. The provider must confirm whether the actual channels and payment methods are available for this business. Scope, fees, and terms are discussed before work. A review is informational and is not a compliance certification. The public form asks for the website, the products, and the question. It does not take a customer list.
Checkout and wholesale channel profile
The two middle columns say what to look up. The last column is for your own figures and methods. Leave a cell blank when that channel is not live or you have not calculated it from paid orders. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Checkout and wholesale channel profile. The last column is for temporary notes.
Fact
What to record for the public checkout
What to record for wholesale or invoiced orders
Your record
How the order is created
What to record for the public checkoutWhether a customer completing checkout creates the order, which is WooCommerce's usual path.
What to record for wholesale or invoiced ordersWhether an administrator adds the order, or the buyer receives an invoice. WooCommerce documents both manual orders and shared invoices.
Who places the order
What to record for the public checkoutThe customer who uses the public checkout, described as that channel and not as a wholesale account.
What to record for wholesale or invoiced ordersThe buyer type or ordering role for the invoiced channel, without a customer name, email address, or other identifying detail.
How payment is requested
What to record for the public checkoutThe payment method shown on the live checkout, including a method that fails to appear.
What to record for wholesale or invoiced ordersThe invoice, bank instruction, or other request you actually send. Name a Stripe Invoice or Payment Link only if that is the tool you use.
Where the payment record sits
What to record for the public checkoutThe provider record that corresponds to the checkout order, kept separate from the store status.
What to record for wholesale or invoiced ordersThe invoice or ledger entry for that buyer. A Stripe Invoice, when used, is a record for a specific customer and is not reused for someone else.
Fulfillment
What to record for the public checkoutHow a paid checkout order is shipped or handed off, if that channel is live.
What to record for wholesale or invoiced ordersHow an invoiced order is shipped, and whether that path differs from checkout. A difference is a fact, not an eligibility finding.
Size from paid orders only
What to record for the public checkoutThe count and amount range from checkout orders that have been paid. Leave blank if there are none.
What to record for wholesale or invoiced ordersThe count and amount range from invoiced orders that have been paid. Do not average this together with checkout, and do not use a forecast.
Live or planned
What to record for the public checkoutWhether the public checkout can take payment today.
What to record for wholesale or invoiced ordersWhether wholesale or invoiced orders are taken today, or only planned. Planned is not history.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Wholesale is not a processing approval, and neither is a working public checkout.
Stripe Invoicing and Payment Links are Stripe products. Do not describe a channel as using them unless it does.
Do not send a customer list, card data, or invoices containing bank details through the public form.
WooCommerce managing orders — checked 2026-09-21. Orders are usually created when a customer completes checkout, and they can be added manually in WP Admin. WooCommerce documents more than one way to pay an order, including sharing an invoice with the customer.
WooCommerce order statuses — checked 2026-09-21. Processing means the store has recorded payment as received and the order is awaiting fulfillment. That status does not say which channel created the order.
Stripe Invoicing — checked 2026-09-21. Stripe describes an invoice as a way to collect from a specific customer, and says an invoice cannot be reused for another customer. It describes a Payment Link as usable by anyone with the link.
Prism solutions — checked 2026-09-21. The provider decides eligibility and account terms. Prism discusses scope, fees, and terms before a processing-preparation consultation.
Prism features — checked 2026-09-21. A website review does not guarantee approval or continued processing and is not a compliance certification.
Prism contact — checked 2026-09-21. The form asks for the website, products, and question, and says to leave out card details, passwords, and customer records. The request does not submit a processing application.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.