Which Sage export fields does a freight quote need?
Key Takeaways
A freight quote needs a clear shipment identity, actual pickup and delivery details, physical freight facts, and relevant service requirements. Your AI logistics coordinator should identify which of those facts the Sage export supplies and who confirms the rest. No single field list applies to every Sage product, shipping mode, or carrier. Start with the real movement. Then map the available source fields to the information needed for an accurate provider request.
- Preserve the sales-order and relevant release references.
- Distinguish the actual ship-to site from the billing address.
- Confirm shipment quantity, units, weight, and mode-relevant dimensions.
- Explain the meaning of pickup and delivery dates.
- Supply service needs and customer approval rules through defined sources.
Your AI logistics employee should not turn a recommended shipment checklist into a claim about native Sage columns. Wilson connects with ERP-based workflows through an environment-specific method and coordinates freight execution. The customer's Sage product and setup determine the available source. Ask Cartage to demonstrate the actual mapping and missing-data path. Do not assume that every field is exported, every value is final, or every Sage environment has the same Wilson connector.
What is the difference between a source field and a freight requirement?
A source field is a place where Sage stores information, while a freight requirement is a fact needed for the movement. Your AI logistics coordinator should connect them without assuming they are identical. A field may hold a requested date, not a confirmed appointment. A weight field may have a defined calculation or meaning that differs from final packed freight. Ask the source owner what the value represents before using it in a quote request.
Your AI logistics employee should also recognize that a required fact may come from outside Sage. The warehouse may supply packed measurements after the order is released. Customer service may confirm receiving restrictions. The commercial owner supplies approved providers and limits. The goal is a complete, reliable shipment basis. It is not to force every fact into an export or pretend the ERP already contains information nobody has recorded.
Written October 31, 2026
Which field groups should the quoting workflow receive?
The workflow should receive the information needed to identify and describe the intended shipment; your AI logistics coordinator should check its meaning and completeness. The table below is a recommended business-input checklist. It is not a Sage schema, a Wilson API specification, or a universal carrier-required template. Confirm the exact fields for the selected mode and provider. Mark absent facts for review instead of inventing values to make the file pass a technical check.
| Field group | Recommended business information | Source or review question |
|---|---|---|
| Source identity | Sage product, relevant company context, order reference | Which business record does this describe? |
| Release relationship | Shipment portion or release reference | Is this the full order or one movement? |
| Readiness | Approved condition for freight work | Is the freight actually intended to move now? |
| Pickup location | Actual origin and relevant contact | Which facility will present the goods? |
| Pickup timing | Ready date and relevant window | Is the value requested, planned, or confirmed? |
| Delivery location | Actual ship-to address and relevant site reference | Is this the receiving site rather than bill-to? |
| Delivery timing | Required arrival condition or appointment information | What commitment is actually needed? |
| Freight description | Useful goods description and relevant mode information | Can the provider understand the freight? |
| Quantity | Handling units and clear units of measure | Does the count mean items, cases, or pallets? |
| Physical measurements | Relevant packed weight and dimensions | Are values final and attached to the correct scope? |
| Service needs | Required loading, handling, or receiving conditions | What affects provider fit or charge? |
| Provider authority | Approved carriers or brokers and customer rules | Which options may be used? |
| Approval route | Named owner for out-of-limit decisions | Who resolves an exception? |
Your AI logistics employee should not treat all blanks equally. A missing optional reference differs from a missing delivery site. A provisional dimension may require review before a final commitment. Define which facts block the next step and which can be supplied later under an approved process. That rule should come from the actual shipment workflow. A generic statement that all columns are mandatory can create needless work while still missing an important service condition.
Should every value be in one row?
Not necessarily; your AI logistics coordinator setup should reflect the source and shipment structure. An order can have several product lines. A shipment can have several handling units with different dimensions. A load can contain several orders. One flat row may omit relationships or repeat information. Agree the actual input design with the source and operations owners. Do not describe a proposed business checklist as a universal file format the product accepts unchanged.
Your AI logistics employee should make repeated records understandable. A repeated order number can represent a new release, another product line, or an unchanged record in a later file. Those are different cases. Define the identifier and grouping rule that distinguishes the intended movement. A technically valid file can still cause incorrect freight work if rows are interpreted at the wrong level. The buyer should inspect the resulting shipment, not just whether the import accepted the file.
Which references should remain separate?
Keep the sales order, customer purchase order, internal shipment, and carrier reference distinct; your AI logistics coordinator should preserve their relationship. Each can identify a different aspect of the same movement. A carrier may not recognize the internal sales-order number. Finance may need that order relationship later. Clear reference types make the workflow easier to use without pretending that one number can replace every other identifier across the customer and provider systems.
Your AI logistics employee should avoid removing meaningful formatting from identifiers without checking the source definition. Some references may include leading characters or other significant elements. The system owner should confirm how values are represented in the agreed input. A display that looks simpler can still alter the business key. Test actual examples through the source-to-shipment path so users can find the record using the reference they already know.
What do official Sage fields establish?
Official field documentation establishes product-specific source definitions, not a complete freight integration; your AI logistics coordinator setup still needs a customer mapping. For Sage 100, the published sales-order header layout includes order, bill-to, and ship-to information. It also identifies a ShipVia field. Those names help the source owner investigate available data. They do not prove the customer's export contains them or that their values are sufficient for every quote request.
How should Sage 100 header fields be used?
Use the documented header fields as source candidates for the relevant business facts. Your AI logistics coordinator should confirm their actual meaning in the customer's setup. The Sage 100 sales-order header layout distinguishes SalesOrderNo and bill-to and ship-to fields. That supports keeping the order identity and address roles separate. The source owner should confirm the exact available fields, values, and export method for the installed environment.
Your AI logistics employee should not turn a ShipVia value into an unreviewed carrier commitment. The field may contribute useful information about a source instruction or code. The operations owner must explain how that information relates to approved providers and service needs. A label inside the ERP does not itself show that the carrier priced or accepted this load. Keep the source instruction distinct from the later execution decision and provider response.
Why must bill-to and ship-to stay distinct?
They can describe different locations and business roles; your AI logistics coordinator should quote the actual freight destination. A customer's head office may receive invoices while its warehouse receives goods. An account can have several receiving sites. Copying a billing address into the quote can create an inaccurate shipment basis. Confirm the intended site with the order owner when the source is unclear. A familiar customer name does not settle the physical destination.
Your AI logistics employee should retain relevant site information beyond the street address when the movement needs it. A receiving reference, contact route, or service condition can affect the carrier request. Ask the appropriate source owner. Do not invent a universal site-validation feature or assume an address alone establishes every access condition. The operational requirement is an accurate description of where and how the carrier is being asked to deliver.
Does a shipping field always contain final shipment information?
No, the source field's meaning and status must be checked; your AI logistics coordinator should distinguish planned, entered, and confirmed information. Sage's Shipping Data Entry overview describes shipment-related entry and review functions in its documented product context. That does not establish what your export supplies or what a particular value means in your workflow. Confirm the source rather than assuming every shipping-related field is final carrier-ready data.
Your AI logistics employee should also distinguish system capability from customer configuration. A product can support a field while a business leaves it unused or stores a local code. An export can omit information present elsewhere in the system. Identify the actual source and owner. The freight workflow should use verified meanings, not infer completeness from the existence of a documented screen or database field. This keeps product research from becoming an unsupported integration promise.
Which physical freight details need special care?
Quantity units, packed measurements, and shipment scope need special care; your AI logistics coordinator should ask for confirmation when their meaning is unclear. These facts can materially affect the provider's offer. A product quantity is not necessarily a pallet count. An item weight is not necessarily the packed load weight. Different handling units can have different dimensions. Use the facts required for the actual mode and provider rather than one assumed formula for every order.
How should weight be described?
Weight should identify its unit, scope, and confirmation status; your AI logistics coordinator should not use an unlabeled number. State whether the value covers one package, one pallet, or the entire shipment. Confirm whether it is a product figure or final packed weight. Ask the warehouse or appropriate source owner if the distinction is unclear. The carrier should understand the freight it is being asked to price, not guess how the shipper intended the number.
Your AI logistics employee should not invent a conversion or packaging allowance to create a precise total. If the business uses an approved calculation, identify its owner and application. If the packed value must be measured, ask for it. A provisional quote may have conditions that need later confirmation. Keep those conditions visible. A clean file with a guessed total can be less useful than an open question that prevents an inaccurate carrier commitment.
How should dimensions and counts be related?
Dimensions should be associated with the handling units they describe; your AI logistics coordinator should avoid an unexplained single size for mixed freight. Several pallets may share dimensions, or each may differ. Confirm what the carrier needs for the intended service. The source design should preserve the relationship without forcing users to infer it from a free-text note. The actual input structure needs agreement with the provider and system owners.
Your AI logistics employee should keep quantity types explicit. An order can list products in sold units while the warehouse supplies cartons and pallets. The carrier may need handling units. Finance later may review a different commercial quantity. These values can coexist without being interchangeable. The workflow should explain which count is used for the quote and how it connects to the shipment. Do not assume that one quantity column answers every operational and financial question.
What about commodity or handling information?
Provide the useful goods description and required mode-specific information from an authorized source. Your AI logistics coordinator should not classify freight by guessing from a product name. Some requirements may need specialist or customer confirmation. Ask who owns that information. Do not promise universal classification, regulatory interpretation, or specialist handling support. The business should confirm the relevant requirement and provider suitability before sending a request that presents uncertain information as settled.
Your AI logistics employee should distinguish a required service from a general product attribute. The order may describe fragile goods without specifying the transport arrangement the customer expects. Ask the owner what the carrier must actually provide. The provider can then confirm its service and terms. Clear instructions support useful quoting. A long unreviewed product description may still leave the most important handling question unanswered.
Which dates, service needs, and approval instructions belong with the quote?
The quote needs the timing and conditions relevant to the movement, plus the customer's decision boundaries. Your AI logistics coordinator should identify their sources and meanings. Some of this information may come from the export. Some may come from a warehouse or approved instruction. Keep requested dates separate from confirmed appointments. Keep approved provider instructions separate from a historical ShipVia code whose current meaning has not been checked.
What should pickup timing say?
Pickup timing should describe when the freight will be ready and any relevant collection window; your AI logistics coordinator should confirm the source. An order date does not establish readiness. A planned production completion may still need warehouse confirmation. Tell the carrier what is requested and what is confirmed. The resulting quote or commitment should fit the actual load rather than an optimistic date copied from a commercial record.
Your AI logistics employee should also identify who supplies changes. A delayed release can affect an existing quote or tender. A carrier may need to reconfirm service. The workflow needs a clear handoff for urgent changes, especially when the source is a daily file. Do not assume the next scheduled export arrives soon enough for every transport decision. The business should define the exception route before relying on the normal source schedule.
What should delivery timing say?
Delivery timing should identify the customer's actual requirement and the status of any receiving arrangement; your AI logistics coordinator should avoid overstating a requested date. A provider may offer an estimate, not a guaranteed commitment. A warehouse may require an appointment that has not been secured. Record those distinctions. A lower quote for a different service is not equivalent to one meeting the required condition, even when the destination address is the same.
Your AI logistics employee should route a proposed timing tradeoff to the authorized owner. A different arrival may be acceptable only after customer or operations approval. Do not let a price comparison silently make that decision. If the requirement changes, confirm the provider's response for the revised movement. Internal approval and carrier acceptance remain separate. The quote input should support both decisions with clear facts rather than assume a date field carries every necessary meaning.
Where should provider and spending rules come from?
They should come from the customer's authorized freight or commercial owner; your AI logistics coordinator should not infer them from incomplete source data. Define approved carriers or brokers, relevant rate targets, and approval limits. Identify exception owners and backups. Use actual customer values. A missing rule should be a visible decision request, not permission for unrestricted sourcing or spending. The workflow needs both accurate shipment facts and a clear authority boundary.
Your AI logistics employee evaluation should distinguish written rules from implemented controls. A policy can say a manager must approve an exception. The buyer must still confirm how the proposed setup enforces or routes that requirement. Ask for a demonstration when it matters. General rule-bound coordination should not be expanded into an unsupported claim about every approval gate, permission feature, or payment block available by default.
How should the export be checked before it is used?
Check the source meaning, identifiers, completeness, and resulting shipment against known examples; your AI logistics coordinator evaluation should inspect the business outcome. A valid CSV can contain the wrong site or describe rows at the wrong level. A spreadsheet can change the representation of an identifier. The source owner and operations should review the mapped result together. The test should show accurate freight information, not merely a file accepted without a technical error.
| Check | Example question | Expected response when unclear |
|---|---|---|
| Record meaning | Is this an order line or a shipment? | Ask the source owner before creating loads |
| Identity | Does the reference preserve the actual business key? | Confirm representation and relationship |
| Address role | Is this the actual receiving site? | Ask the authorized order owner |
| Measurement scope | Does this weight cover one unit or the full load? | Ask the physical shipment source |
| Timing meaning | Is the date requested or confirmed? | Preserve uncertainty and seek the right fact |
| Repeat input | Does this record refer to existing freight work? | Follow the demonstrated change process |
| Authority | Is the option within customer rules? | Route the exception to its owner |
Your AI logistics employee test should include incomplete and changed records. Remove a required measurement and observe the next action. Resend an existing order and inspect how prior work is recognized. Change an accepted shipment and examine the impact review. These are requirements to demonstrate in the proposed setup. Do not infer universal validation, duplicate prevention, or change handling from the fact that a source file can be received.
What should the test packet contain?
The test packet should contain authorized source examples, expected shipment facts, and known missing information; your AI logistics coordinator should be evaluated against those expectations. Use the actual Sage product and a representative order structure. Handle sensitive information under company procedures. Identify the target provider decision and approval rule. The buyer should know what a correct result looks like before the demonstration starts, rather than define success around whatever the presenter shows most easily.
Your AI logistics employee evaluation should inspect what remains manual after mapping. The warehouse may still confirm packing. A manager may still approve a rate exception. Another person may perform a source-system update. Those steps can be appropriate if clear. Record them. The useful finding is an accurate workflow with understood responsibilities. A structured export does not prove every field and decision becomes automatic.
How does Wilson fit the field discussion?
Wilson fits as an AI logistics coordinator that connects order information with carrier execution under customer rules. Ask Cartage to show the actual input fields, missing-data questions, and resulting quote request. Confirm the Sage environment and source method. Detailed validation and return updates should be agreed and demonstrated. Do not confuse a recommended shipment checklist with a native Wilson schema or a guaranteed connector for every Sage product.
Your AI logistics employee evaluation can connect the input with BOL and POD links to ERP orders. For later evidence, review POD collection from carriers. Stable references and clear shipment facts matter throughout the movement. The quote input should help later teams understand what shipped and what was agreed. Finance should not need to reconstruct the relationship from old files.
How should the field list change as the workflow grows?
Change the field list only when the business identifies a useful new requirement or source improvement. Your AI logistics coordinator should not accumulate columns without a purpose. A new mode may need different freight facts. A new site may add a receiving condition. A recurring missing detail may belong in the source handoff. Name the owner and test the effect. Keep definitions understandable so users know what each value means and when it is confirmed.
Your AI logistics employee review should use actual blocked or corrected cases. Ask whether the problem came from an absent field, unclear units, wrong source, or misunderstood record structure. These causes need different fixes. Do not assume more columns always improve the process. Use the smallest reliable input that supports the defined movement and authority. Keep a clear path for facts and decisions outside the export.
How should a field-mapping sheet be written?
A useful mapping sheet names the business fact, actual source, meaning, and owner. Your AI logistics coordinator setup should not rely on matching column names alone. Identify the source field or approved external input. State its units and whether it is requested, planned, or confirmed. Name the person who resolves an absent or conflicting value. This can remain a concise working document. Its purpose is to make the shipment interpretation reviewable, not create another data-entry exercise.
Your AI logistics employee evaluation should use that sheet to inspect a real authorized example. Ask the source owner to show the value and operations to explain its use in the carrier request. If their meanings differ, resolve the disagreement before relying on the transfer. A technical field can be available while still being inappropriate for the proposed shipment fact. The mapping should preserve the business meaning rather than make the target record look complete at any cost.
Which fields should stay outside the carrier request?
Keep unrelated commercial or personal information out of the request unless the approved workflow requires it. Your AI logistics coordinator should use the information needed for the freight decision. An order export may contain details useful elsewhere in the business. Their presence does not mean every carrier needs them. Define the relevant handoff and follow the company's access and information-handling procedures. This is a practical scope requirement, not a claim of a particular default security control or certification.
FAQs
Which Sage export fields does a freight quote need?
It needs the source and release references, actual locations, relevant timing, physical freight facts, and required service information. Your AI logistics coordinator should identify the export's contribution and missing-data owners. The exact fields depend on the Sage product, shipment mode, carrier, and customer process rather than one universal schema.
Can we use the bill-to address as the delivery destination?
Only if it is confirmed as the actual receiving site; your AI logistics coordinator should not assume those address roles are identical. Official Sage 100 documentation distinguishes bill-to and ship-to information. Confirm the relevant destination and receiving conditions for the actual shipment before quoting or tendering.
Does Sage's weight field always provide final packed freight weight?
Do not assume that; your AI logistics employee setup should confirm the field's meaning, units, scope, and source. The value may not represent the final packed movement required for the quote. Ask the system and warehouse owners to verify it rather than infer completeness from a shipping-related label.
Does this checklist prove a native Sage integration with Wilson?
No, a recommended input checklist does not establish a connector or supported schema. Wilson is an AI logistics coordinator with an environment-specific ERP connection method. Confirm the actual source, mapping, missing-data path, and any return updates with Cartage before relying on the proposed workflow.