Manufacturing · Building Materials and Architectural Products

EDI and API Integration for Stone, Quartz and Countertop Manufacturers

Stone, quartz and countertop producers sell slabs and surfaces to fabricators, distributors and builders, with lot and slab-level detail that matters to the installer. ECOM connects orders, slab and lot data, freight and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in stone, quartz and countertop

Products

  • Quartz and engineered stone slabs
  • Granite, marble and natural stone
  • Prefabricated countertops
  • Sinks, edges and accessories

Business models

  • Producers and importers selling to fabricators
  • Distributors serving kitchen and bath dealers
  • Builder and project programs

Scenarios

Where stone, quartz and countertop manufacturers lose time and margin

Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.

  • Slab-level identification

    The problem
    Each slab is individually identified, and customers select by lot or bundle.
    How ECOM helps
    ECOM carries slab, bundle and block or lot identifiers from your ERP onto the 856.
    What you gain
    Fabricators receive the slabs they selected, identified on the notice.

    Talk to an EDI/API Expert about slab-level identification Share a sample 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Very heavy, fragile freight

    The problem
    Slabs ship on A-frames and crates with special handling, and claims need clear records.
    How ECOM helps
    ECOM builds crate and bundle detail into the 856 and compares it with your pick data before the shipment leaves.
    What you gain
    Receiving differences and freight claims can be researched against the notice.

    Talk to an EDI/API Expert about very heavy, fragile freight Share a sample 856 Advance Ship Notice and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.

  • Project-based demand

    The problem
    Projects drive timing and mix of orders.
    How ECOM helps
    ECOM posts project-driven orders and changes as they arrive.
    What you gain
    Project timing changes reach allocation and shipping.

    Talk to an EDI/API Expert about project-based demand Share a sample 850 Purchase Order and 860 Purchase Order Change Request, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for stone, quartz and countertop manufacturers

Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.

Fabricators
Order slabs by lot.
Distributors and showrooms
Stock and resell.
Builders and designers
Specify and buy.
Quarries and overseas producers
Supply raw slabs.
Specialty carriers
Haul slabs.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for stone, quartz and countertop manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Fabricator or distributor→Your plant and ERP 850 Purchase Order Material, thickness and quantity by area or slab.
  2. Fabricator or distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Fabricator or distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Fabricator or distributor 856 Advance Ship Notice Crate, bundle and slab detail with lot.
  5. Your plant and ERP→Fabricator or distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Quarry or overseas producer 850 Purchase Order Purchase orders for slabs and stone with quantities and requested delivery dates.
  7. Quarry or overseas producer→Your plant and ERP 856 Advance Ship Notice Slab, crate and bundle detail with the supplier’s block or lot, used to plan receiving and match slabs to jobs.

The diagram draws the exchanges between the lanes shown. Motor-carrier and warehouse documents (204, 990) are listed in the table below with the direction each travels.

  1. Slab orders

    Orders (850) specify material, thickness and quantity.

  2. Allocate bundles

    Bundles or slabs are allocated by lot.

  3. Ship notice

    The 856 lists crates, bundles and slabs.

  4. Invoice

    The 810 bills by slab or area.

  5. Inbound supply

    Producer orders (850) and notices (856).

EDI and API exchanges

The documents behind the workflow

X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.

DocumentDirectionWhat it carries for stone, quartz and countertop manufacturers
850 Purchase Order You receive Material, thickness and quantity by area or slab.
860 Purchase Order Change Request You receive Changes to open orders: quantities, dates or cancellations.
855 Purchase Order Acknowledgment You send The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
204 Motor Carrier Load Tender You send Tenders a truck shipment to a motor carrier.
990 Response to a Load Tender You receive The motor carrier’s acceptance or decline of the tender.
856 Advance Ship Notice You send Crate, bundle and slab detail with lot.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Purchase orders for slabs and stone with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Slab, crate and bundle detail with the supplier’s block or lot, used to plan receiving and match slabs to jobs.

Other exchanges you may meet

  • Fabricator portals
  • Forwarder status

Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.

Operational detail

Slabs, lots and special freight

Slab and lot identifiers move from receiving to allocation to shipment, and a mismatch means a fabricator receives material that does not match what it chose. Slabs ship on A-frames and in crates, so crate-level detail also supports freight claims.

  • Dimensions and units of measure

    Products sell by the piece, box, square foot, linear foot, pallet or bundle. Orders, ship notices and invoices must agree on units and conversions, or quantities and prices disagree.

  • Jobsite and yard delivery

    Deliveries go to branches, yards and jobsites, sometimes with delivery appointments or special equipment. Ship-to detail and carrier information are part of the exchange.

  • Distributor orders

    Most volume moves through distributors, dealers and home centers that send their own orders, changes and inventory or sales data.

Connected systems

Systems that send and receive this data

Documents are only useful when they reach the systems that run the business.

  • ERP with slab inventory
  • Warehouse management
  • Transportation management
  • Fabricator portals

Onboarding and monitoring

From first requirement to daily exception handling

  1. Confirm the requirement

    Obtain each partner's implementation guide or specification, for example from your fabricator or distributor, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP with slab inventory and warehouse management so the data posts without re-keying.

  3. Test with the partner

    Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.

  4. Validate, acknowledge and monitor

    A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.

  5. Resolve exceptions

    Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.

Example exceptions for stone, quartz and countertop manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Slab on an order is no longer in inventoryThe order line can be held for review and substitution options are shown so the team can offer a matching slab before shipping.
Crate or bundle detail differs from the ship noticeA comparison of crate or bundle detail on the 856 with the pick can flag a mismatch for review before the shipment leaves.

Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.

How ECOM helps

ECOM products and services that apply

Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.

  • PRISM-EDI

    Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.

  • PRISM-WebEDI

    Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.

  • PRISM-SmartConvert

    Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.

  • PRISM-SCV

    Monitoring of transactions and exceptions across customer and supplier documents.

Frequently asked questions

Can slab-level data be exchanged?

Where the customer asks and your inventory system holds it, slab and bundle identifiers can be mapped into documents, so fabricators receive the lot they selected.

Do fabricators use EDI?

Some do; many use portals, email or files. ECOM supports a mix, so you can serve large fabricators and small shops with the same inventory.

How are units of measure and conversions kept consistent?

Item and unit conversions are agreed during mapping, so a quantity ordered in boxes can be shipped and invoiced in the unit the trading partner expects. They are part of the partner’s implementation guide and tested before go-live.

Do you need our trading partner's implementation guide to start?

It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.

Talk to an EDI/API expert about stone, quartz and countertop manufacturers

Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.