SOFTWARE + PAYMENTS
ECI Spruce payment integration
Payment integration review for ECI Spruce: a counter sale, a contractor account, and any deposit or remaining invoice balance.
About the integration
ECI Spruce supports lumberyards and building-material suppliers across counter sales, inventory, and business operations. PayPact reviews the payment workflow for contractor purchases and account collections, where a counter ticket, delivery order, and outstanding invoice may need different treatment.
Supported products
- ECI Spruce
Features
Trade-counter workflow+
Review how the payment amount and reference move between the sales process and the checkout device.
Contractor-account collections+
Identify how on-account purchases and later payments should be handled without confusing them with immediate counter sales.
Yard and delivery context+
Account for order changes, delivery timing, and returns when defining payment and refund procedures.
How it works with PayPact
Start with a counter sale, a contractor account, and any deposit or remaining invoice balance. PayPact works with your team to confirm the supported payment connection, the identifiers it uses, and the records it updates. Before launch, we walk through a real example and agree where staff handle receipts, exceptions, and refunds. Software functions outside that agreed payment flow remain in ECI Spruce.
Requirements
What you’ll need+
- An active ECI Spruce environment and an administrator who can confirm the product, access permissions, and deployment.
- A sample workflow covering a counter sale, a contractor account, and any deposit or remaining invoice balance, with sensitive customer and payment details removed.
- An approved merchant account and a confirmed gateway, processing platform, and connection scope. Any required provider permissions must be in place.
Setup
Walk through the collection process+
Show us how your team handles a counter sale, a contractor account, and any deposit or remaining invoice balance. We identify the collection point and the records that must stay aligned.
Confirm the connection and responsibilities+
Validate the available path for your ECI Spruce environment. Agree the payment methods, access requirements, costs, and responsibility for each setup step.
Test with the people who use it+
Run the agreed payment, receipt, and correction scenarios with your staff. Confirm which records update automatically and which need a manual step before launch.
FAQs
Is this a native ECI payment module?+
We do not describe it as native without confirming the implementation. PayPact reviews the supported connection for your Spruce environment, including any required software-provider involvement.
Which payment methods can we use with ECI Spruce?+
We confirm methods for the specific connection and merchant account. Card, ACH, wallet, stored-payment, and in-person options are not assumed to be available together.
What determines the cost and setup timeline?+
Your ECI Spruce configuration, transaction needs, and any required connector or hardware determine the scope. PayPact reviews processing and additional costs before you commit to implementation.
Epicor
Integrated payment support for Epicor BisTrack, Eagle, and Prophet 21 across counter sales, customer accounts, accounts receivable, and ecommerce workflows.
View details
Odoo
Connect Odoo invoices, customer portals, and online checkout to card and ACH payments through PayPact, with Dual Pricing available.
View details
SAP
Payment support for applicable SAP ERP, retail, hospitality, and checkout environments.
View detailsMarketing copy is based on public product information. Confirm technical compatibility, version coverage, and available payment methods before publishing or implementation.
CONFIRM YOUR CONFIGURATION
Let's review how ECI Spruce fits.
Bring us the software version, current payment setup, and the workflow you want to improve. We will help identify the most practical supported path.
Find your fit