A House Bill of Lading or Master Air Waybill can contain all the right shipment data and still come out wrong.
The consignee address wraps into the wrong place. A customer reference disappears. Handling instructions don’t print as expected. A logo looks misaligned. One customer wants a particular statement on every document, while another needs a completely different layout. Then someone fixes the output manually in Word or PDF, and the same problem comes back on the next shipment.
For freight forwarders, these aren’t just cosmetic issues. HBL and MAWB documents carry operational, commercial, and sometimes regulatory information. CargoWise can generate bills of lading, air waybills, invoices, packing lists, and other commercial documentation directly from booking and job data, but getting the final output right depends on the data, document configuration, and customization behind it.
This is where CargoWise macros, document customization, and custom document templates become important.
Why do HBL and MAWB Formatting Problems Happen in CargoWise?
When a CargoWise document doesn’t look right, it’s tempting to blame the document template immediately. But the visible formatting issue is often only the final symptom.
The problem may originate from the shipment data itself, the field or macro pulling that data, conditional document logic, customer-specific requirements, organization settings, or the structure of the document template.
That distinction matters because simply moving a field around won’t permanently solve a data or configuration problem.
Before changing an HBL or MAWB, the first question should therefore be:
Is the wrong information being retrieved, or is the correct information being displayed incorrectly?
Those are two completely different problems.
What are the Most Common CargoWise HBL Formatting Problems?
House Bills of Lading often require more customer-specific customization because they’re issued by freight forwarders and may need to reflect company branding, contractual requirements, destination requirements, and customer instructions.
Common HBL formatting problems include shipper or consignee addresses overflowing their allocated space, notify-party information appearing incorrectly, container or package details not aligning properly, inconsistent descriptions of goods, missing references, incorrect footer statements, unwanted blank sections, and company branding that doesn’t fit the intended layout.
There may also be situations where the same HBL template is being used across customers whose document requirements are very different.
Trying to accommodate every scenario within one poorly structured template can make document maintenance increasingly difficult.
What are the Most Common MAWB Formatting Problems?
MAWB problems can be even more sensitive because air waybill content needs to align with airline and regulatory requirements.
For example, CargoWise has continued updating air waybill behavior as compliance requirements evolve. In 2025, CargoWise introduced alerts when non-compliant cargo descriptions are entered on MAWB/HAWB documents, reflecting tighter cargo-description expectations associated with programs such as ACAS.
CargoWise has also previously introduced changes affecting MAWB content for specific compliance scenarios, such as automatically handling required dangerous-goods information and country-specific data requirements.
This illustrates an important point: not every MAWB output issue should be solved by simply customizing the printed document.
Sometimes the underlying CargoWise data or current product behavior needs to be reviewed first.
Where do CargoWise Macros Fit into Document Customization?
A custom document isn’t useful if users still have to type the same shipment information into it manually.
This is where CargoWise macros become valuable.
Macros allow document configurations to reference information already stored within CargoWise. WiseTech’s learning resources specifically include guidance for users who need to identify CargoWise data field names, maps, and macros, showing how closely these elements are connected with system configuration and customization.
In practical terms, document customization can use the appropriate available data references to populate information such as shipment parties, job references, routing information, operational details, and other relevant data into the output.
The objective is straightforward:
Enter the data correctly once and reuse it wherever possible.
That reduces duplicate typing and helps keep the document aligned with the underlying CargoWise job.
Why does Macro Selection Matter?
Choosing the wrong data reference can produce a document that looks perfectly formatted while displaying the wrong information.
For example, a business may have several organization-related addresses or references available within its CargoWise configuration. If the document pulls from a source that doesn’t match the intended business rule, users may repeatedly correct the document manually even though the template itself appears fine.
That’s why good document customization starts with understanding:
- What information should appear?
- Where is that information stored?
- Which data source should control the output?
- Under what conditions should it appear?
- What should happen when that information is blank?
The last question is particularly important.
A well-designed template needs to account for exceptions instead of assuming every shipment contains identical data.
When do You Need a Custom CargoWise Document Template?
Standard documents may work well for standard operations. But freight forwarding rarely stays standard for long.
A custom document template may become useful when your company has specific branding requirements, customers require particular document layouts, different business units need different outputs, additional operational information needs to appear, or existing documents require too much manual editing before they can be sent.
The goal, however, shouldn’t be customization for the sake of customization.
Every additional template creates something that needs to be governed and maintained. A better approach is to understand which requirements can be handled through standardized configuration and which genuinely justify a separate document design.
CargoWise’s certification framework itself includes Document Customization Fundamentals within its Core Configuration competencies, alongside workflow configuration and EDI/XML integration.
That reflects how document customization should be treated: as part of system configuration rather than basic graphic design.
Can One Template Handle Different Customers?
In many cases, the better question isn’t, “Can we create another template?”
It’s, “Can the existing document intelligently handle the difference?”
Suppose Customer A requires a specific reference, Customer B requires additional instructions, and Customer C needs a particular document statement.
Creating three entirely separate documents may work initially, but multiply that across dozens of customers and branches, and template maintenance can become difficult.
Where supported by the underlying document configuration, thoughtful conditional logic and data-driven customization can help produce different outputs based on relevant business requirements.
This can reduce unnecessary template duplication while maintaining customer-specific document behavior.
Why should You Avoid Manually Editing HBLs and MAWBs After Generation?
Sometimes manual editing feels like the quickest solution.
Generate the document. Export it. Change the text. Fix the alignment. Send it.
Done.
Except the same issue returns tomorrow.
Repeated manual correction introduces several problems. Users spend additional time on documents, the final version may no longer perfectly reflect the data held in CargoWise, different employees may make different changes, and it becomes harder to standardize document quality across branches.
CargoWise is designed to create commercial documentation directly from operational data and link documents with shipment workflows. Its eDocs capability also provides centralized electronic document creation, capture, storage, and access.
If a document requires the same manual correction every time, that’s a strong signal to investigate the underlying configuration.
How can Document Formatting Affect Automation?
This is where document customization becomes much more important than appearance.
Modern CargoWise operations increasingly depend on workflows, electronic messaging, integrations, and automated document handling. CargoWise workflows can be configured around shipment mode, lane, direction, customer, milestones, and other operational requirements.
A properly configured document process can therefore fit into a wider workflow in which data is captured correctly, the appropriate output is generated, documents are stored in eDocs, and relevant parties receive the required information.
Poorly designed customization does the opposite. It creates exceptions that users have to resolve manually.
The best CargoWise document isn’t simply the one that looks good.
It’s the one that consistently produces the right output with as little manual intervention as possible.
What should You Check Before Customizing an HBL or MAWB?
Before rebuilding a document, review the problem systematically:
- Source data: Is the required information correctly maintained in CargoWise?
- Data reference: Is the document retrieving information from the appropriate field or source?
- Business rules: Should the information always print, or only under certain conditions?
- Layout: Does the template provide enough room for realistic data lengths?
- Customer requirements: Is this a genuine customer-specific need or something that should be standardized?
- Compliance: Is CargoWise already controlling the field because of a carrier, customs, or regulatory requirement?
- Testing: Has the document been tested against different shipment scenarios rather than one ideal example?
This approach helps solve the actual cause rather than repeatedly patching the output.
How Elicit Helps with CargoWise Macros, DocBuilder and Custom Document Templates?
Document customization can quickly become complex when HBLs, MAWBs, customer requirements, macros, workflow rules, branding, and operational data all need to work together.
As an official CargoWise Service and Business Partner, Elicit Technology helps freight forwarders review and customize CargoWise documents around their actual operational requirements. Our CargoWise specialists can help identify why document outputs aren’t behaving as expected and determine whether the issue sits with source data, macros, configuration, document logic, or the template itself.
We support CargoWise macros, DocBuilder and custom document templates, along with workflow configuration, forwarding setup, reporting, automation, integrations, and broader CargoWise customization. Instead of leaving operators to repeatedly correct documents manually, the goal is to build a standardized solution that produces accurate, professional outputs directly from CargoWise.
Conclusion
HBL and MAWB formatting problems often look simple on the surface. Move a field, change a font, add a line, and the problem appears solved.
But permanent fixes usually require a deeper look.
The source data needs to be correct. The right CargoWise data references or macros need to be used. Document logic needs to reflect the business requirement. Templates need to accommodate real shipment scenarios. And MAWB changes must be considered carefully where CargoWise behavior is tied to airline or regulatory requirements.
If your team regularly reformats HBLs, corrects MAWBs after generation, maintains too many customer-specific templates, or can’t get CargoWise documents to produce the output you need, the underlying customization may be ready for a review.
Schedule a call with an experienced CargoWise Service Partner such as Elicit Technology can help turn repetitive document fixes into a properly configured, scalable document process, so your team spends less time fixing paperwork and more time moving freight.
