# See every pallet, and turn today's orders into loads without leaving the building.

> Roadmark receives against customer ASNs, keeps a location for every pallet, bills storage by the pallet each month, and turns outbound orders into loads.

URL: https://roadmark.ai/warehouse
Language: en

Roadmark receives against your customers' ASNs, keeps a location for every pallet, bills storage by the pallet each month, and turns outbound orders straight into loads your carriers tender on. Run it as light warehousing beside your transportation, or connect the WMS you already run.

## Receive against the ASN and flag whatever doesn't match.

Every inbound trailer is checked against the ASN the customer sent. A short pallet or a damaged case doesn't wait for someone to notice at month end: the exception goes to the customer with photos, the same day.

## Orders due today become tomorrow's load.

Orders due today are grouped by destination. When a group is ready, it becomes a load in the TMS with its stops already set, and goes out for tender without anyone re-keying an address.

## Storage bills itself off the same pallet count.

Positions held, pallets handled in and out, and any accessorial are totalled from the same warehouse activity at month end, not rebuilt in a spreadsheet.

## Already run a WMS? Keep it, and sync through it.

Orders, inventory and receipts move by EDI or API from the WMS you already run, so Roadmark plans transportation on real, current stock without becoming your warehouse system of record.

- **The order to ship** An outbound order arrives from your WMS as a 940, and Roadmark turns it into a load.
- **Confirms what shipped** A 945 goes back once the load leaves, with the pallets and pieces that actually went.
- **A transfer inbound** Stock moving in from another location arrives as a 943 and becomes an ASN to receive against.
- **Confirms what was received** A 944 goes back with what the warehouse actually received against it, exceptions included.

## Run receiving and storage in Roadmark. Keep transportation how it is, or add it.

Start with just the warehouse, beside the TMS or WMS you already run, and bring in outbound tendering when you're ready.

## Questions about the warehouse.

- **How does Roadmark handle receiving discrepancies?** Every inbound trailer is checked against the customer's ASN, and a short pallet or damaged case is drafted to the customer with photos the same day, instead of waiting to be noticed at month end.
- **How do outbound orders become loads?** Orders due today are grouped by destination, and once a group is ready it becomes a load in the TMS with its stops already set and goes out for tender, without anyone re-keying an address.
- **How is storage billed?** Positions held, pallets handled in and out, and any accessorials are totalled from the same warehouse activity at month end, not rebuilt in a spreadsheet.
- **Can Roadmark connect to our existing WMS?** Yes. Orders, inventory and receipts move by EDI (940, 945, 943 and 944) or API from the WMS you already run, so Roadmark plans transportation on real, current stock without becoming your warehouse system of record.
- **Can we start with just the warehouse and add transportation later?** Yes. Run receiving and storage in Roadmark beside the TMS or WMS you already run, and bring in outbound tendering when you're ready.

## Related pages

- [Cross-dock](https://roadmark.ai/cross-dock): Floor, staging and load plans
- [Billing and settlements](https://roadmark.ai/billing): Invoices, driver pay and carrier pay
- [Customer and carrier portals](https://roadmark.ai/portals): Each side sees only its part
- [EDI X12 integration: 204, 990, 214 and 210 explained](https://roadmark.ai/integrations/edi): What EDI 204, 990, 214 and 210 mean, which way each goes and when it's sent, how trading partners are set up, and how tracking status becomes 214s.

Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.