Shipping and returns documents look simple until a retrieval system has to answer a customer-specific question. A shipping policy may contain delivery zones, exclusions, processing times, carrier caveats, and product-specific rules. A returns policy may combine eligibility requirements, time limits, refund methods, condition requirements, and regional exceptions. If these sections are chunked as long pages, a WooCommerce assistant can retrieve relevant words without retrieving the rule that changes the answer.
For agencies building customer support, storefront search, or order-service workflows, the objective is not merely to split policy text into equal-sized pieces. The objective is to preserve each decision the policy makes and the conditions attached to it.
Why policy documents need deliberate chunking
A customer rarely asks for the whole policy. Typical questions are narrower:
- “How long does standard shipping take to Canada?”
- “Can I return a sale item after 14 days?”
- “Who pays return shipping for a defective product?”
- “Does free shipping apply to oversized items?”
The answer to each question may depend on several nearby or distant sections. A chunk containing only “returns are accepted within 30 days” is incomplete if another section limits that rule to unused products and excludes final-sale items. Chunking should keep the primary rule, its conditions, and its exceptions together whenever possible.
Identify policy units before choosing chunk size
Start by identifying the logical units in the source document. Common units for WooCommerce shipping and returns content include:
- Processing times, which describe how long an order takes to leave the warehouse.
- Transit times, which describe carrier delivery after dispatch.
- Shipping methods, including service levels, costs, and eligible destinations.
- Geographic zones, such as domestic, international, remote, or restricted areas.
- Product exclusions, including oversized, hazardous, perishable, customized, or downloadable goods.
- Return eligibility, including deadlines, item condition, packaging, and proof of purchase.
- Refund and exchange procedures, including timing, payment method, and deductions.
- Exception rules, such as damaged goods, incorrect items, refused deliveries, and force majeure events.
These units are better chunk boundaries than arbitrary character counts. A section titled “International Shipping” should normally remain intact with its introductory rule and its related bullet points. If the section is very long, split it by destination or service rather than in the middle of a condition.
Separate independent policy decisions
One useful pattern is to create a chunk for each independent decision. For example, the following text contains a complete shipping rule:
Example shipping chunk: Standard orders shipped within the contiguous United States are processed within two business days and usually arrive within three to five business days after dispatch. This service is unavailable for Alaska, Hawaii, and P.O. boxes. Oversized products may require a separate freight quote.
This chunk can answer processing, transit, geographic, and product-exception questions without requiring the entire shipping page. The metadata can identify it as a shipping rule and preserve the relevant scope.
A separate chunk should handle a different decision:
Example returns chunk: Unused physical products may be returned within 30 calendar days of delivery. Items must include original packaging and accessories. Personalized products, gift cards, and final-sale items are not eligible for change-of-mind returns.
Do not combine unrelated shipping and returns rules merely because they appear on the same page. A customer asking about a delayed parcel should not receive a large context block dominated by refund instructions.
Keep conditions and exceptions attached
Conditions are often expressed in headings, lead-in sentences, tables, or footnotes. Detaching them creates unsafe answers. For example, a chunk containing “Free shipping on orders over $100” is incomplete if the next line says “excluding oversized products and orders shipped to remote areas.” Keep the offer and exclusions in one chunk, or repeat the governing condition in both related chunks.
For long sections, use controlled overlap. A destination-specific chunk can repeat the policy scope in a short prefix:
Shipping policy: delivery estimates exclude order-processing time and may vary during peak periods.
That repeated context is more useful than indiscriminate overlap across an entire page. A small semantic overlap of one or two sentences is usually preferable to copying a large token window that introduces unrelated rules.
Handle tables as structured policy content
Shipping policies frequently store the most important information in tables. A row such as “Canada | Express | 2–4 business days | Duties unpaid” should not be embedded without its column labels. Convert the row into self-contained text before indexing:
Destination: Canada. Service: Express. Estimated transit time: 2–4 business days after dispatch. Import duties and taxes: paid by the recipient unless otherwise stated.
For return-fee tables, include the same context:
Return reason: change of mind. Eligible window: within 30 days of delivery. Return shipping: paid by the customer. Refund deduction: original shipping charges are non-refundable.
Preserve units, currencies, date types, and qualifiers. “30 days” should not lose whether the policy means calendar days or business days. “Delivery time” should not be rewritten as “processing time.”
Use metadata that reflects WooCommerce operations
Metadata gives retrieval and downstream workflows additional filters without forcing every fact into the prose. Useful fields include:
policy_type:shipping,returns,refunds, orexchangesregion: a country, state, shipping zone, orglobalproduct_scope:all-products,oversized,personalized, or another catalog classificationservice_level:standard,express,freight, orpickupeffective_fromandeffective_until: dates used to prevent retrieval of retired rulessource_urlandsource_heading: provenance for support agents and auditspriorityorexception_type: values that help rank an exception above a general rule
Keep metadata values consistent with WooCommerce configuration. If the store uses shipping zones named “US Domestic” and “Canada,” use those names or a controlled identifier rather than inventing alternate labels during ingestion.
Chunk for the question, not only the document
Retrieval quality should be tested with questions that reflect real support traffic. Include positive and negative cases:
- “What is the standard delivery time to California?” should retrieve processing and transit information for the applicable domestic zone.
- “Does express shipping include weekends?” should retrieve the express-service rule and any business-day definition.
- “Can I return a personalized mug?” should retrieve the personalized-product exclusion, even if the general return window is also relevant.
- “Who pays for a damaged item?” should retrieve the defective-item procedure rather than the change-of-mind return rule.
When an exception should override a general policy, make that relationship explicit in the text and metadata. A chunk can state: “This is an exception to the general 30-day change-of-mind return rule.” That phrasing improves semantic retrieval and helps a response system distinguish precedence.
Account for policy versioning
Shipping rates and return windows change. Indexing a new policy without retiring the old chunks can produce contradictory answers. Store a policy version, publication date, and effective date with every chunk. During retrieval, filter out chunks whose effective period does not include the current date, or rank the currently effective version above archived content.
When a policy is updated, reprocess the complete logical section rather than modifying only the sentence that changed. This avoids leaving old exceptions, headings, or table context in the index. Keep the source URL and heading so an agency team can trace an answer back to the published policy.
A practical ingestion sequence
- Parse the source document and retain headings, lists, tables, links, and footnotes.
- Normalize table rows into labeled, self-contained text.
- Classify sections as shipping, returns, refunds, exchanges, or general terms.
- Split sections at semantic boundaries such as destination, service, product type, or exception.
- Attach conditions, exclusions, and effective-date information to every applicable chunk.
- Add controlled overlap only where a preceding definition is required to interpret the next rule.
- Assign consistent WooCommerce-oriented metadata.
- Run retrieval tests using actual customer questions and adversarial exception cases.
- Remove or down-rank expired chunks when the policy changes.
For agencies using LlamaParse with an Undefined-based retrieval workflow, the important handoff is the normalized policy unit rather than the original page layout alone. Preserve the source location for citations, but index text that can stand on its own when retrieved.
Validate answers against policy precedence
Before deploying a support workflow, test whether specific rules outrank general rules. A product exclusion should override the standard return window. A destination restriction should override the general free-shipping offer. A defective-item process should not be replaced by the customer-paid return instruction for change-of-mind orders.
Useful acceptance criteria include complete answers, correct units and dates, correct regional scope, explicit uncertainty when no rule applies, and a source reference for the support agent. Chunking is successful when the retrieved context contains enough information to make the correct decision without pulling in contradictory or obsolete policy text.