A customs software review should start with the point at which cross-border deliveries actually fail: not at the border, but in the order data long before a parcel is collected. A missing commodity code, an unclear product description or the wrong delivery terms can turn a promising international order into a delayed parcel, an unexpected charge or a poor customer experience.
For growing UK retailers, wholesalers and consumer brands, customs technology is no longer a back-office consideration. It directly affects conversion, fulfilment speed, carrier performance and the confidence customers have when ordering from abroad. The right solution makes international shipping feel more controlled. The wrong one can add another disconnected system for operations teams to manage.
What a Customs Software Review Should Assess
The first question is simple: what do you need the software to do? There is a meaningful difference between a specialist customs declaration platform and a multi-carrier delivery platform with customs capabilities built into the shipping workflow.
A standalone platform may be the right choice for businesses managing complex import and export declarations, high freight volumes or specialist customs regimes. It can offer deep declaration functionality and granular controls for a dedicated customs team. However, it may also require order, warehouse and carrier data to be passed between several systems before goods move.
For parcel-led eCommerce operations, that separation can create friction. Shipping teams often need customs data to be validated at the same time as labels are created, carrier services are selected and customer notifications are triggered. In this case, the strongest option is usually the one that connects product, order and carrier data in a single operational workflow.
A useful review therefore looks beyond a feature checklist. Ask where customs information originates, who owns it, how it is checked and whether it travels with the shipment without manual rekeying. Software cannot correct poor data forever, but it should make issues visible before they become expensive exceptions.
Product data is the real starting point
Commodity codes, country of origin, item descriptions, quantity, weight and declared value are not administrative extras. They determine how a shipment is assessed and whether it can move cleanly through a destination market.
Look for tools that make it practical to maintain this information at product level and reuse it across orders. A platform should support clear data rules rather than relying on a warehouse operative to remember what needs entering for each destination. The best workflows flag gaps early, preserve an audit trail and make it easier to apply consistent descriptions across channels.
The level of control required depends on your catalogue. A brand shipping a narrow range of own-label products may need straightforward product master data. A marketplace seller with thousands of changing SKUs, bundled products and multiple suppliers will need stronger mapping, validation and governance.
Carrier connectivity matters as much as form generation
Customs data must meet the requirements of the carrier carrying the parcel. Different services, lanes and destination countries can require different data fields, document formats or commercial invoice rules. If a system produces information that does not align with the chosen carrier service, the operational benefit quickly disappears.
This is why a customs solution should be assessed alongside carrier connectivity. Can your team compare delivery services and select the right option without leaving the platform? Does customs data flow directly into the label and electronic shipment record? Can the system support a shift in carrier if performance, cost or capacity changes?
Businesses with a single carrier and a small set of destination markets may accept a more limited setup. Brands expanding across Europe and further afield need flexibility. Carrier choice should not mean rebuilding customs processes every time a new service is introduced.
Customs Software Review: Questions That Reveal the Gaps
A supplier demonstration can make almost any workflow look straightforward. The more revealing test is to use your own real-world scenarios: a mixed basket, a return from Europe, a high-value order, a delivery to a remote destination and a shipment where an item’s origin differs from its shipping country.
Ask the provider to show what happens when data is incomplete. Does the order stop before collection? Is the reason clear? Can an authorised user correct it quickly? A good exception process protects speed without allowing incomplete shipments to pass unnoticed.
It is also worth examining how delivery terms are handled. DDP and DAP are commercial choices with a direct customer impact. Under DDP, duties and taxes are generally managed before delivery, helping create a more predictable checkout and doorstep experience. Under DAP, the recipient may be asked to pay charges before the parcel is released. Neither approach is universally right, but the software should make your chosen approach operationally clear by market, carrier and service.
For businesses selling into the EU, consider how the platform supports VAT-related data and schemes relevant to your model, including IOSS where applicable. For exports from Great Britain, ensure the process fits the information needed for declarations through the appropriate channels. Good technology supports compliance, but it does not remove the need for accurate classifications, sound tax advice and clear commercial policies.
Integration Should Reduce Work, Not Move It Elsewhere
The value of customs software is often decided by its integration model. If teams have to export orders from an eCommerce platform, enrich them in a spreadsheet, upload them to customs software, then create labels in a carrier portal, the operation is vulnerable at every hand-off.
Look for direct, maintainable connections to the systems that matter: eCommerce platforms, marketplaces, ERP systems, warehouse management systems and carriers. The goal is not integration for its own sake. It is a single, reliable flow from order capture to dispatch, delivery and returns.
A multi-carrier platform can be particularly valuable here because it brings shipping execution and customs data together. Clearview, Team AGL’s proprietary platform, is designed to give businesses one operational layer for carrier access, label generation and cross-border parcel management. That model is especially useful when growth means adding carriers and territories without adding separate portals and repetitive processes.
Integration quality should also be judged by what your people can manage day to day. Can operations teams change service rules without a development project? Are shipping rules transparent? Can finance and customer service see the status needed to answer a query? Technology that only works when a specialist is available will struggle during peak trading periods.
Visibility Has to Extend Beyond Dispatch
A shipment is not successful simply because it has left the warehouse. For international orders, operations teams need to identify customs holds, missing information, duty-related delays and failed delivery attempts quickly enough to act.
Your review should cover reporting and tracking as seriously as declaration capability. Look for shipment-level visibility, clear exception statuses and data that can be filtered by destination, carrier, service and reason for delay. This helps teams spot recurring problems, whether that is a product description issue, a carrier-specific requirement or a destination market that needs a different delivery proposition.
Customer-facing visibility matters too. Customers do not distinguish between a customs delay, a carrier delay and a retailer delay. They simply know their order has not arrived. Proactive updates and a clear support process can protect the relationship, but only when the underlying delivery data is accessible and trustworthy.
Returns deserve the same attention. A cross-border return can create additional documentation, cost and customer frustration if it is treated as an afterthought. Check whether the proposed solution supports your returns routes, gives your team visibility of inbound parcels and avoids sending customers through an unnecessarily complicated process.
Make the Decision Around Your Operating Model
There is no universal winner in a customs software review. The best choice depends on your shipment profile, product range, destination markets, internal expertise and the role international delivery plays in your growth plans.
A business with a dedicated trade compliance function and intricate customs requirements may benefit from specialist declaration depth. A fast-growing retailer shipping high parcel volumes across multiple carriers may gain more from a connected platform that removes manual work from order processing and keeps delivery choice open.
Before committing, define the outcomes you expect to improve. That might be fewer customs exceptions, less time spent on label creation, lower abandoned baskets caused by unclear duty treatment, quicker carrier onboarding or better support for international returns. Then test whether the platform can deliver those outcomes using your operational reality rather than an idealised workflow.
The strongest customs technology does not make international delivery feel more technical. It gives your team the confidence to sell into new markets, offer customers clearer choices and keep parcels moving when the pressure is on.