Partner access
Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.
Manufacturing integration
How EDI and API integration with True Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with True Homes.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific True Homes program or a customer relationship.
Tell us which documents you exchange with True Homes, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with True Homes.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Material suppliers, trade contractors, building product distributors and software teams that work with True Homes, and the purchasing, field and accounts-payable staff behind them.
True Homes is a semi-custom homebuilder headquartered in Monroe, North Carolina, building across the Carolinas, and operating a trade partners program for suppliers and contractors. ECOM's directory lists it under home building. Home builders buy lumber, windows, appliances, flooring and trade labor for many communities at once, and pay suppliers per job, lot or purchase order.
True Homes builds personalized homes from curated plans and publishes a Partner with True Homes page for trade partners. For a supplier or trade partner the program is purchase orders by community and lot, delivery confirmation, invoicing against the order and payment or remittance; True Homes may route this through procurement software or a supplier portal rather than classic EDI.
No True Homes supplier, vendor or integration document was read for this guide, so the documents, X12 version, delivery method and testing steps below are typical practice for this kind of company: confirm each with True Homes. ECOM helps confirm your trading program, map the required documents, configure connectivity and complete testing against the applicable specifications, then monitors every file after go-live, as software, as a managed service or both.
Workflows
General guidance: typical flows in this industry, not True Homes' published process.
Documents and APIs
General guidance. We could not verify True Homes' EDI requirements from a published source, so these are documents commonly exchanged in this industry, not True Homes' confirmed requirements. Confirm the list, versions and programs with True Homes.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 850 | Purchase Order | From True Homes | Not stated | General guidance | Typically places an order with ship-to, quantities, requested dates and pricing. |
| 855 | Purchase Order Acknowledgment | To True Homes | Not stated | General guidance | Typically confirms, changes or rejects each order line. |
| 810 | Invoice | To True Homes | Not stated | General guidance | Typically bills for what shipped, matched against the order. |
| 820 | Payment Order/Remittance Advice | From True Homes | Not stated | General guidance | Typically carries payment and remittance detail that closes open invoices. |
| 832 | Price/Sales Catalog | To True Homes | Not stated | General guidance | Typically carries item, price and catalog changes. |
| 997 | Functional Acknowledgment | Both directions | Not stated | General guidance | Typically confirms each file was received and could be read. |
Connectivity
Builders often buy through a procurement or supplier portal. Confirm whether orders and invoices can also arrive as EDI or API files.
General guidance
Where files are accepted, they commonly move over SFTP or AS2 with remittance detail by invoice.
General guidance
Challenges
A trade partner program implies onboarding documents before the first order.
Every order and invoice must carry the community, lot and cost code the builder uses, or payment is held.
Payment can depend on lien waivers and delivery proof, so invoices and supporting documents must travel together.
Negotiated price books change by region and community and must match what is on the order.
True Homes's specific documents, version, identifiers and testing steps are not on this page. Confirm each with True Homes before you build maps.
Automation options for True Homes suppliers
ECOM helps you automate them, meet True Homes' labeling and ship notice requirements, and see what needs action. True Homes sets its program's rules; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM connects the documents you exchange with True Homes to your ERP, warehouse and finance systems, so orders, notices and invoices move without re-keying and exceptions are visible early.
See how ECOM supports construction and building product suppliers.
SolutionAutomate orders, invoices and matching between buyer and supplier.
SolutionAutomate invoices, remittances and payment documents.
Zero Trust for EDI and file transfer
Exchanges with True Homes move business documents between your systems and an outside party. A Zero Trust design assumes no connection, file or user is safe by default.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up payment, shipping or reporting.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.
Documents are verified when they arrive and every transfer is logged.
Late, missing or rejected files raise an alert and go to a named owner.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. True Homes may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are True Homes' to set; this is the general sequence most programs of this kind follow.
850 Purchase Order
From True Homes to you
Typically places an order with ship-to, quantities, requested dates and pricing.
855 Purchase Order Acknowledgment
From you to True Homes
Typically confirms, changes or rejects each order line.
820 Payment Order/Remittance Advice
From True Homes to you
Typically carries payment and remittance detail that closes open invoices.
997 Functional Acknowledgment
Both directions
Typically confirms each file was received and could be read.
Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.
Next step
Each request goes to an ECOM EDI specialist with True Homes' name attached, so the reply starts from your program.
Send us True Homes' guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each True Homes document, then go live with monitoring from the first file.
Plan testing and certificationLabels and ship notices that match True Homes' rules, to help avoid receiving problems and compliance deductions.
Review shipping complianceYes. Its website lists a Partner with True Homes page. Confirm the process there.
Companies of this type commonly exchange EDI or API files with partners. This guide does not include True Homes's requirements; confirm the documents and connection with True Homes.
Typical documents are 850, 855, 810, 820, 832, 997. That is general practice, not a published True Homes list; confirm the set with True Homes.
Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on True Homes's requirements, test cycles and your ERP.
No. This is an integration guide based on typical industry practice. It does not indicate a customer, partner or endorsement relationship between ECOM and True Homes.
This guide summarizes publicly available information as of November 2026. True Homes sets its own requirements and can change them at any time; your True Homes implementation guide, supplier portal or account contact is the authoritative source for your program.
True Homes is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with Legend Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Legend Homes.
How EDI and API integration with Lennar Corp. typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Lennar Corp.
How EDI and API integration with LGI Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with LGI Homes.
How EDI and API integration with M/I Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with M/I Homes.
How EDI and API integration with Maronda Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Maronda Homes.
How EDI and API integration with Mattamy Homes typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Mattamy Homes.
Tell us about your True Homes program, documents and ERP. We will outline the connection, mapping and testing plan.