Payment planning

Payment and Quote Readiness

Non-final guidance for payment questions, quote approvals, invoices, deposits, taxes, delivery, installation, and staff-confirmed project payment terms.

Current public reference

This page is payment preparation guidance only. It does not publish final deposit amounts, payment schedules, refund rules, cancellation terms, quote-validity periods, GCT treatment, currency exchange handling, financing promises, or online-payment obligations. Final payment terms should be confirmed on the official quote, invoice, or written staff communication.

Quick facts

  • Page role: Preparation, not final policy - Use this page to understand what payment details should be clarified before committing.
  • Final authority: Official quote or invoice - The website can prepare customers, but staff-confirmed documents should control the actual transaction.
  • Important to confirm: Scope, tax, delivery, installation - Those items can change the final amount and payment expectations.
  • Future bridge: Structured payment fields later - The costing-app bridge should eventually store payment status without taking public payment rules from page copy.

Payment information should support better quotes

Customers should know which payment details to ask about before approving windows, doors, railings, showers, vanities, and custom woodwork. The public page can explain the topics that matter without making final commitments online.

Official documents should control the transaction

The website, builder, gallery, and quote form are starting points. Final payment expectations should be confirmed on a staff-reviewed quote, invoice, receipt, or written approval that matches the actual product scope and site requirements.

Keep future API fields separate from public policy

When the website eventually connects to the costing application, it can pass structured fields such as quote status, deposit status, balance status, payment method, invoice number, and customer approval state. Those fields should track the transaction, not replace staff-approved payment terms.

Payment Details To Confirm

  • Official quote or invoice number
  • Customer name, project address, and contact details
  • Product scope, measurements, drawings, and accepted options
  • Deposit or payment schedule if applicable
  • Balance timing and project milestone expectations
  • GCT, delivery, removal, installation, site visit, or travel charges
  • Currency, payment method, and receipt expectations
  • Change-order, cancellation, refund, and quote-validity wording

Payment Topics To Finalize

These are planning topics, not final payment rules. Each item should be confirmed by Exquisite staff and reflected in the official quote, invoice, receipt, or approval flow.

Quote Status and Approval

A website request, builder configuration, WhatsApp message, or gallery reference should not be treated the same as an approved quote.

  • Clarify when a request becomes an official staff-reviewed quote.
  • Confirm whether measurements, photos, drawings, or a site visit are still required.
  • State that final pricing can change when scope, measurements, product options, access, or installation conditions change.
  • Keep approval language tied to the quote or invoice, not general website copy.

Deposits and Milestones

Deposit and milestone language should be precise because it affects manufacturing, scheduling, and customer expectations.

  • Confirm whether a deposit is required for the specific project before production, procurement, or scheduling.
  • Confirm when any remaining balance is due and what milestone triggers it.
  • Avoid publishing one universal payment schedule until management approves it for all relevant product categories.
  • Make sure any future costing-app bridge stores payment stage without inventing public-facing policy.

Taxes, Currency, and Payment Methods

Tax, currency, and payment method handling should match accounting practice and the official invoice.

  • Confirm whether GCT or other charges are included or itemized on the quote or invoice.
  • Confirm accepted payment methods before presenting them as public policy.
  • Confirm currency handling and exchange-rate treatment before publishing USD/JMD wording.
  • Make receipts and payment references easy for staff to match to the customer record.

Delivery, Installation, Removal, and Travel

Payment expectations can change when the job includes delivery, travel, installation, removal, unusual access, or work outside normal logistics.

  • Confirm whether delivery, removal, installation, travel, or site visits are included, optional, or separately itemized.
  • Capture parish, access notes, floor level, parking, lift/stair access, and site readiness before finalizing logistics.
  • Avoid implying that every quote includes installation or delivery unless the official quote says so.
  • Use the service-area page to collect location context before staff confirms logistics.

Changes, Holds, Cancellations, and Refunds

Change-order and cancellation language should be reviewed carefully before public release.

  • Confirm how scope changes are approved after a quote is accepted.
  • Confirm what happens if measurements, product selections, finish choices, or site conditions change.
  • Do not publish cancellation, refund, restocking, or production-hold terms until they are finalized.
  • Keep written staff confirmation as the record for any approved project change.

Future Online Payments

Online payments should wait until the website has final terms, clear receipts, secure processing, and costing-app reconciliation.

  • Do not add public checkout until payment terms, privacy, receipts, and internal accounting workflows are approved.
  • Plan for secure payment-provider records rather than storing card details in the website.
  • Keep quote approval, invoice creation, and payment reconciliation explicit in the future API bridge.
  • Make customer-facing payment status clear without exposing internal costing data.

Before Discussing Payment

The cleanest payment conversation starts from a clear quote scope. Customers and staff should confirm these details before treating payment expectations as final.

  • Confirm the product category, measurements, drawings, finish choices, glass choices, and hardware direction.
  • Confirm whether the quote includes installation, removal, delivery, travel, site visit, or special access requirements.
  • Ask staff which quote or invoice version is current before making payment.
  • Ask how taxes, currency, payment method, receipts, and balance timing are handled for the specific project.
  • Keep written confirmation for any change in scope, timing, payment stage, or project hold.
  • Do not use website estimates, gallery inspiration boards, or builder configurations as payment approval without staff review.

Related Planning Pages

Website terms
Understand how website estimates, quote requests, and product information should be bounded.

Request a quote
Send structured details so staff can prepare or review official pricing.

Project process
See how references, measurements, photos, and staff review move toward a quote.

Privacy planning
Payment and quote records should fit the future data and costing-app bridge plan.

What to prepare for a window quote

  • Width and height for each opening
  • Room name or location for each window
  • Preferred style such as slider, casement, awning, or fixed
  • Glass and frame color preference
  • Photos from inside and outside where possible

Common Questions

Is this the final payment policy?

No. This page is payment-readiness guidance only. Final deposit amounts, payment schedules, refunds, cancellations, quote validity, tax handling, currency handling, and payment methods should be confirmed by Exquisite staff.

Are builder or website estimates payment approvals?

No. Website estimates and configurations are planning tools until staff reviews the scope and issues an official quote, invoice, or written approval.

What should I confirm before paying?

Confirm the official quote or invoice, project scope, measurements, taxes, delivery, installation, payment schedule, balance timing, accepted payment method, and receipt process.

Can payment terms change by project?

They may need to be confirmed by project because product type, size, custom manufacturing, site logistics, delivery, installation, and scope changes can affect expectations.

Should online payments be added now?

Not yet. Online payments should wait until final terms, privacy language, secure processing, receipts, and costing-app reconciliation are designed together.

How does this help the future API bridge?

It identifies the fields the website should eventually pass to the costing app, such as quote status, invoice reference, payment stage, payment method, and staff approval state.