Company details are required on the wrong checkout path

Give the company field a specific job

Identify who uses the value after the order and what they use it for: naming the ordering organization, preparing an internal purchasing record or identifying the receiving business. These are purposes to establish from your operations, not reasons to assume every buyer has a company. If nobody can name the downstream task, the field's business purpose remains unconfirmed.

Separate an operational preference from a documented buyer requirement. If your actual purchase rules require an organization, removing the field alone does not resolve the buyer-control question. If the field is needed only for a particular organizational workflow, record that scope. Do not instruct buyers to enter invented company names or filler text just to pass validation.

Inspect the assigned checkout before choosing a control

WooCommerce documents company-field visibility and required-field settings in the Checkout block's linked Checkout Fields and address settings. First confirm that the page you are editing is the checkout assigned in Advanced settings. Record the installed checkout type and the configuration you can actually see. A setting on an unused page will not describe the buyer's live path.

A documented company setting does not establish a conditional rule for every buyer category or payment route. If you need company information to be required only on one path, establish whether the installed version and any extension support that condition. Do not assume a global field setting recognizes organizational buyers, or that a custom control also runs on an express wallet path.

Keep hosted custom fields within their documented limits

If the store actually uses Stripe-hosted Checkout and proposes a custom company field, its custom-field documentation permits up to three fields using text, numeric or dropdown types. They are required unless marked optional. Inventory the custom fields already used before promising space for another one, and make the optional setting an explicit part of the requirement.

Stripe says these fields must not collect sensitive data or information restricted by law. A request for company information is not permission to collect identity documents, credentials or unrelated private information there. The hosted custom-field feature also does not prove that your store connector saves the answer into the order field your staff expects. Field collection, storage and the business's processing eligibility remain separate questions.

Decide from the path and the resulting record

For each real buyer path, record whether the company input appears, whether it is required and which existing order field receives the answer. Compare an actual affected order or documented validation report with the configuration. If no order was created, a buyer's error report establishes the reported obstacle, not a storage result. An empty company field on an existing order does not by itself identify why it is empty.

A justified requirement with supported behavior can be scoped to the paths that need it. A preference without a requirement may support an optional field, subject to the store's actual buyer controls. A necessary conditional requirement that the installed checkout cannot establish remains a design gap; do not replace it with a mandatory field everywhere or an undocumented bypass.

Bring the purpose, affected checkout path, observed requirement and missing storage evidence to a Prism checkout consultation. That makes the requested review concrete. Agree on any configuration or implementation responsibilities, scope, fees and terms before work; collecting a company name is not a provider approval or a buyer-verification result.

Company-field requirement map

Complete a separate copy for each real checkout path. Compare the business requirement with the supported control and an existing order or observed validation result. Mark missing evidence unverified rather than entering a fictional company or placing an order solely to fill the sheet.

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.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.