Apartment or receiving-unit details disappear after payment
Find the last existing record that contains the delivery-unit detail and the first downstream record that does not. Compare the same order and the same shipping field across the path your integration actually uses. Keep billing details separate. If only a message or label display omits the detail, check the underlying record before calling it lost data. A missing address line does not prove truncation: the actual field limit or mapping must be established by the implementer.
For: A research-only store owner whose real order or shipping handoff is missing an apartment, suite or receiving-unit detail the buyer says they entered.
Begin with the affected order and the buyer’s report. Identify whether the detail was entered in shipping address line two, a company field, an order note or another field. Those purposes are not interchangeable. A receiving instruction in an order note should not be assumed to become part of the shipping destination.
WooCommerce documents configurable address2 visibility in its Checkout block settings. Check the assigned checkout page and the address settings for that block if it is the path involved. Current visibility helps explain what the checkout offers now; it does not prove which value a past buyer entered or what the configuration was at the time.
Stripe’s hosted Checkout flow documents shipping customization within its feature boundaries. That does not establish that a particular connector collects the unit field or forwards it to fulfillment. Name the checkout type, installed connector and path used by the affected order before applying either platform’s documentation.
Compare connected records, not every address you can find
Use the order reference to locate the records for that purchase. In authorized systems, compare any retained checkout evidence, the order’s shipping fields, the relevant provider shipping record if one exists, the fulfillment handoff and the destination used for the label. Record the time and version of each. A customer profile edited later is not proof of what the original order contained.
Do not assume that the provider sits between the store and fulfillment. Your connector may use the store order directly. Ask the maintainer to identify which record supplies the shipping handoff. A provider record containing only billing information is not evidence that a shipping unit was lost there.
For each connected pair, record whether the unit detail is present, absent or not observable. Compare values privately and keep only the finding and record location in the worksheet. If an earlier record is unavailable, report the gap: a buyer’s account of entering the detail is useful evidence, but it is not a retained checkout payload.
Separate a missing value from a missing display
When the stored shipping address includes the unit but the confirmation message does not, investigate the message’s source or presentation. When the fulfillment record includes the unit but the label does not, investigate the label handoff or display. Neither observation establishes that the order itself lost the value.
If the order contains the detail and the actual fulfillment input does not, the known gap lies at that handoff. If the order is the earliest available record and already lacks it, the loss cannot yet be localized more precisely. Give the implementer that boundary instead of naming a plugin as the cause.
An omitted line, an overwritten field and a shortened value are different observations. For suspected truncation, ask for the actual field limit, where it is enforced and the evidence that the affected value exceeded it. Do not invent a universal character limit or squeeze a unit into an unrelated billing field. A limit in one template is not evidence of a limit in order storage.
Correct the destination that fulfillment will actually use
Before changing a paid order, establish who is authorized to confirm the destination and which systems still need the correction. Record the original evidence and the authorized change. Updating a customer profile or store order alone does not establish that an already-created fulfillment instruction or label was updated.
If shipment has already left, treat the request as a delivery-change question for the responsible fulfillment party or carrier. Do not describe an order edit as a rerouted parcel. For an unshipped order, the operational owner should establish the correct destination in the record that will be used before releasing that handoff under the store’s process.
After an authorized repair, confirm the corrected real record at each affected boundary. A matched order and shipping handoff closes that comparison for that order; it does not prove every checkout path works. A Prism checkout consultation can start with the path, field and first confirmed mismatch. Confirm investigation and implementation responsibilities, scope, fees and terms before work, without sending customer addresses through the public inquiry.
Address-line continuity
Follow one real order along its confirmed data path. Compare full addresses only inside authorized systems; write present, absent, different or not observable here, with a non-sensitive record reference. The first mismatch narrows the investigation only when the two records are actually connected.
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.
Address-line continuity. The last column is for temporary notes.
Checkpoint
Record to compare
Decision the comparison supports
Your finding
Checkout line purpose
Record to compareField label, billing or shipping purpose, actual checkout path and retained evidence if available.
Decision the comparison supportsDistinguish a collected shipping unit from a note, hidden field or unsupported recollection.
Order address line
Record to compareOriginal order shipping fields and any dated edits.
Decision the comparison supportsIdentify whether the detail reached the order; do not use the current customer profile as historical proof.
Provider address field
Record to compareRelevant shipping field, if the provider actually participates in this shipping data path.
Decision the comparison supportsMark not applicable when the visible provider field is only billing or the provider is outside the handoff.
Fulfillment destination
Record to compareThe actual record or export consumed by the fulfillment service.
Decision the comparison supportsA complete order beside an incomplete fulfillment input identifies the handoff to investigate.
Label or confirmation display
Record to compareDestination stored by the shipping tool compared privately with the label or delivered message.
Decision the comparison supportsAn omitted display line can exist while the underlying record remains complete.
Suspected length limit
Record to compareImplementer’s documented limit and the affected field comparison, without copying its address.
Decision the comparison supportsLeave truncation unproven until the limit and its enforcement point are known.
Correction authority
Record to compareAuthorized destination confirmation, change owner and current shipping stage.
Decision the comparison supportsIdentify every dependent record needing correction; an order edit does not reroute a dispatched parcel.
Corrected handoff evidence
Record to compareDated comparison of the corrected real order and destination used for fulfillment.
Decision the comparison supportsClose only the observed mismatch and retain any path that remains unverified.
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.
Limits
WooCommerce Checkout block settings and Stripe hosted Checkout features describe different integrations; neither proves the installed connector’s mapping.
No address-field length, cause of data loss or successful carrier redirection is established by this guide.
Keep customer addresses, private tracking links and order exports out of the worksheet and public consultation form.
WooCommerce Checkout block — checked 2026-09-29. The assigned checkout and linked address settings matter; company, address2 and phone visibility are configurable. This does not establish a historic field value, custom-field behavior on every path or a truncation limit.
Hosted Checkout flow and line-item responsibilities — checked 2026-09-29. Hosted Checkout offers shipping and other customizations within defined boundaries. Feature presence does not prove connector support or the merchant’s actual address mapping.
Prism solutions — checked 2026-09-21. Prism discusses storefront and processing questions within an agreed scope; responsibilities, fees and terms are confirmed before work.