Request a Quote documentation

1. Initial setup

Expected result: eligible product pages show the quote action and the quote page can submit a validated request without creating an order.

2. Customer request flow

1. Open an eligible product and choose required variations or product options.
2. Add the item to the quote list and review the confirmation.
3. Open the quote page, adjust quantities and complete the configured request fields.
4. Submit the request. The customer sees the new request number; no order or payment is created.

When country rules are configured, complete the billing-country picker or the existing field mapped to billing.country. Mapped fields keep their configured visibility conditions: an absent country uses the chosen unknown-country fallback. A rejected country preserves the list and details so they can be reviewed. If rules changed, reload the list before retrying. A committed request retried with the exact same data returns its original receipt.

Copying products from the normal cart is a separate action and leaves that cart intact. The confirmation changes to Request received only when submission succeeds; the unsent-selection notice then disappears. If a connection fails, keep the existing form and retry instead of starting a second request.

Try this flow in Plugin Lab ↗

3. Working draft, design and templates

Open a request from the queue. The working draft can update line quantities, proposal unit prices, per-line and overall discounts, charges, introduction and commercial terms. The presentation screen controls layout, accent color, company identity, logo, signature graphic and footer.

Template workflow

• Save the current presentation as a named template.
• Apply a template to another working draft.
• Export/import presentation data; customer details and economics are excluded.
• Publish a revision only after the HTML and PDF previews are correct.

A published revision is immutable. Continue editing in the working draft and publish a new revision when needed.

Open the real design editor ↗

4. Notifications and delivery

Request receipts, administrator notifications, proposals, replies and decision notices use separate stored delivery records. Retries reuse the same snapshot and do not silently create a new revision.

• Administrator To, visible CC and hidden BCC are validated independently.
• Customer copies are optional and are not backfilled when enabled later.
• The proposal attachment must match the published revision and its recorded hash.
• Provider delivery, inbox placement, DKIM and message reading require external evidence; local interception does not prove them.

5. Acceptance and WooCommerce orders

The private link lets the recipient view and decide on one published revision. Acceptance preserves that revision, terms and totals. It does not charge the customer.

1. The merchant reviews the accepted agreement.
2. Current product availability and guarded economic rules are checked again.
3. The plugin creates at most one linked WooCommerce order.
4. WooCommerce provides the customer payment link and owns gateway processing, status and refunds.

If a payment is declined, use Prepare my order again to review availability and retry the same order. This does not change the accepted proposal. A native completed payment after reservation expiry is held for merchant review without automatically allocating stock; do not pay again while that review is pending. Gateway cancellation handling can differ: with tested Stripe 11.0.0 defaults, a succeeded event already queued before cancellation is automatically refunded by Stripe’s deferred worker and the order stays cancelled. Check both the WooCommerce order and gateway record before retrying or refunding; these checks do not certify every late-delivery or provider configuration.

For bank transfers, the proposal shows that confirmation is awaited; placing the order is not confirmation that funds were received.

Rejecting a proposal can collect customer feedback without creating an order.

6. Privacy, access and retention

• Quote data is stored locally in dedicated plugin tables and order metadata.
• WordPress personal-data export and erasure integrations cover the documented quote records.
• Private links are bearer links, not identity verification. Expire or revoke them when appropriate.
• Controlled deletion requires an archived request, exact confirmation and no blocking linked order or in-progress delivery.
• Uninstall retention follows the explicit plugin setting; WooCommerce orders are not deleted by Request a Quote.

7. Troubleshooting

8. Quote-list tools and saved selections

After adding an eligible product, follow the confirmation dialog or the configured redirect to the dedicated quote list. A quote list is separate from the normal cart and has not been sent until the request form succeeds. The list indicator shows the current product selection.

• Review quantities, concrete variations, supported product options and optional desired prices. Configure which product details and columns appear in the list; hiding a detail does not change its stored value.
• For supported variable products, the multiple-variation grid lets customers review selected rows before confirming the whole addition. Unavailable or invalid rows reject the addition.
• PDF and data exports describe the current list. They do not submit a request, publish a proposal or create an order.
• Account customers can save favorite selections and review them before adding them back. Current catalogue and audience rules are checked again.
• A shared-selection link previews products before an explicit addition to the recipient’s own list. The owner can expire or revoke it. Anyone holding the link can use its permitted actions; it is not identity verification, and does not promise frozen product prices.

9. Request details and admission rules

Configure customer fields, required contact details, billing-country admission and the inline or popup request form. The popup retains entered details when closed or when validation fails. Configure the allowed attachment types, sizes and quotas before enabling uploads; an uploaded file alone is not a submitted request.

Spam controls and provider-backed challenges require their own valid configuration. An unavailable provider is not proof that a challenge passed. Product, customer, country, quantity, stock and cart conditions are checked on the server, even when the request button is visible.

Use the Rule simulator for saved product and role decisions. It does not impersonate a customer: individual account exceptions and other request conditions can make the result conditional.

10. Queue, follow-up and controlled automation

Use request search, filters, assignment and waiting status to organize work. Published revisions remain immutable; editing a draft does not update a customer’s existing proposal.

Configure automatic-offer and reminder rules explicitly before enabling them. Review their settings, timing, message content and delivery history, and keep the site’s scheduled processing operational. These tools do not guarantee inbox delivery and do not charge a customer. Quote acceptance, WooCommerce order creation and payment remain separate actions.

Retention rules act on eligible records under the documented order and delivery guards. Review the policy and preserve a backup before changing it. Export and erasure features are scoped integrations with WordPress privacy tools, not a claim of complete legal compliance.

11. Review settings before importing

1. Export portable preferences from the source store.
2. Preview the destination changes, including product selection, country admission and purchase-button visibility.
3. Resolve destination-specific products, pages and available integrations.
4. Confirm the reviewed changes only while the destination settings version is current. If another save occurred, reload and review again.

Current settings exports use format20. Older supported files preserve destination choices for fields absent from their format. Settings transfer is separate from exporting design templates and from moving customer requests or orders.

12. Current verified scope

This handbook describes candidate version 1.0.1. Supported Product Options & Add-Ons Pro files (PDF, PNG or JPEG, up to 4 MiB each and ten option files per request) are retained privately with the quote. Native order lines keep readable choices and private file references without adding their fees again. Linked-product accessories and other file formats require separate compatibility work. Focused tests cover the editor, three PDF layouts, templates, logos, signature graphics, revisions, notifications, decisions, guarded order creation, classic/Block checkout and the named theme matrix. Broad third-party compatibility and external provider delivery remain separate evidence.

Product page → · Admin demo guide → · Customer demo ↗