Proposals

Proposals are the customer-facing presentation of a project, and they represent the final step in the sales process before signature and payment.

For a simple explanation of how Stripe payments work, read Payment Methods.

What the customer can do

• review quoted items
• open line-item details
• approve or reject items when customer approval is required
• sign the proposal
• pay deposit, balance, full amount, or a custom amount depending on configuration
• review the invoice view

Measurement Approval

Individual measurements can carry their own customer approval state:

• Unreviewed
• Accepted
• Rejected

This is important because customer feedback may block parts of the sale even when the overall project is still active.

Payment Behavior

The customer payment flow is Stripe-backed and can create payments for:

• deposit
• full payment
• balance payment
• custom payment

Payment records then move through their own state lifecycle, such as Pending, RequiresAction, Completed, or Failed.

Payment Methods

The customer portal currently supports Stripe payment methods such as:

• credit or debit card
• ACH bank transfer

Card payments are usually faster.

ACH payments usually take about 4 days to confirm, and sometimes longer.

If a payment still shows Pending, the money is not fully confirmed yet.

Projects do not move forward until the payment is confirmed.

For the plain-language version of this explanation, see Payment Methods.

E-sign Behavior

Tempr supports e-sign sessions as part of the proposal flow. Signature templates and envelope handling are managed through the e-sign module and its admin panel, while customers experience the signing step inside the proposal flow.

Practical Guidance For Internal Users

• make sure the project customer record is correct before sending the proposal
• verify totals and approval-sensitive measurements before asking a customer to sign
• use the invoice view when the customer needs a post-sale financial summary
• expect payment behavior to change based on whether prior payments already exist on the project