In UAE Free Zones, Your Inventory Record Is Part of Your Customs Record

In a United Arab Emirates (UAE) free zone, customs records and inventory records describe the same physical goods. A length of pipe arrives at a yard in Dubai's Jebel Ali Free Zone (JAFZA). It has a specification, an HS code, a customs declaration reference, an owner, a location and a storage period that starts when it is offloaded. Each of those facts belongs to the same item, so they belong in the same history.

This article focuses on JAFZA. Procedures differ between free zones, so the detail should be checked for each one.

Where customs, yard and finance teams keep separate records, the same information is entered several times and reconciled by hand. Billing slows down, and every movement, re-export or mainland release adds to the reconciliation work.

Automating customs declarations on their own does little to fix this. If the warehouse still runs on spreadsheets, the bottleneck simply moves. The stronger model runs customs data, stock and warehouse events from one shared history.

Every free-zone operator should be able to answer three questions at any moment:

• What stock do we hold, and whose is it?
• What is the customs position of each item?
• What storage charges have accrued, and can we evidence them?

When customs and inventory sit in separate systems, answering all three at once takes manual reconciliation. At volume, that work falls on the people best placed to handle exceptions, customer queries and compliance decisions.

Why customs and inventory are linked in JAFZA

Free zones let goods be imported, held, transferred and re-exported with duty treatment that differs from a direct entry into the UAE mainland (UAE Government). That flexibility is exactly why the records matter so much.

JAFZA is home to more than 11,000 companies from over 150 countries (Khaleej Times). A warehouse or yard there often holds goods for many customers at once. Items arrive, sit, move between locations, change owner, ship back out or cross into the mainland.

Dubai Customs requires free-zone companies holding a customs business code to run an inventory system compatible with its own requirements (Dubai Customs). The stated aim is to make customs inventory audits easier, with inventory reports that line up with Dubai Customs' records. The requirement also covers logistics and clearance companies storing goods for customers in Dubai's free zones.

In practice, the inventory history must remain traceable to the customs declarations supporting it. The data the warehouse uses to manage stock is also the evidence that goods are accounted for.

The record needs to distinguish customs movements, yard activity and storage time

A JAFZA operator handling goods for multiple customers deals with three kinds of event:

• Customs movements: arrivals declared under a Bill of Entry, re-exports, and transfers to the mainland or another zone. Each carries the documentation obligations set by Dubai Customs.
• Yard activity: offloading, shifting stock between blocks, inspection and other handling. These change where goods are and what condition they are in, without necessarily changing their customs status.
• Ownership and storage time: goods changing customer inside the zone, and the days each item spends on site, which feed storage charges.

Each has different consequences, so the record needs to tell them apart while keeping them in one history. Recording each event once, in one place, avoids rebuilding the same history later for customs, the yard and finance.

A note on 12-digit HS codes

The UAE is moving from 8-digit to 12-digit HS codes under the GCC Integrated Customs Tariff. Dubai Customs set out a phased rollout in Customs Notice 10/2025, starting in August 2025. Its later phases bring in imports from free zones and customs warehouses to the local market, then imports from the rest of the world (Dubai Customs).

In January 2026, Customs Notice 02/2026 extended the flexibility to use 8-digit codes until further notice, and Dubai Customs continues to accept declarations using them (Dubai Customs). Dubai Customs guidance also states that shipments destined for free zones remain on 8-digit codes (Dubai Customs).

For a JAFZA operator, that means goods can enter under an 8-digit code and later need a 12-digit code if they are released to the mainland once the rule applies. Recording both codes in the item's classification history means the right code is ready when the goods are released.

What goes wrong when the workflow is split

A common set-up looks like this. The customs team works in the declaration system, the yard team in a spreadsheet or WMS, and finance in the billing system. Each holds a partial copy of the truth, and keeping them aligned takes manual effort.

Why the split happens

The split usually reflects how an operation grew. Customs teams own declaration workflows, and warehouse teams own a WMS or spreadsheets. Neither system was built to hold the other's data, so any link between them tends to be a manual export and import that runs daily or weekly.

At low volume, that lag is manageable. With many customers and high-value items in the yard, a customer asking about the customs position of one batch should get an answer from the record, without a day spent gathering data.

Where it breaks down

The failure points are predictable:

• the same data rekeyed at every hand-off, with each entry a new chance of error
• spreadsheets that are the only place an item's ownership history or yard location exists
• storage charges calculated from stock data that doesn't reflect recent movements or the customer's agreed charging terms
• customs status that can't be confirmed without someone going to check
• customer queries that need several people to answer
• audit requests that require item histories to be rebuilt from emails, spreadsheets and system exports

The cost lands in three places.

Billing. Storage charges depend on the customer's agreement. Some contracts use the stock held on a specified billing date. Others charge pro rata for the time goods remain on site, so a partial release or mid-month arrival changes the calculation. When the movement data and the contract terms sit in different places, statements take longer to produce and are harder for customers to check.

Audit. Operators need to show how stock on site relates to the declarations under which it entered and left. If, for example, the yard shows 47 lengths of pipe against a declaration for 50, someone has to work out whether three were released, moved or miscounted. Where records have drifted, teams rebuild that history by hand, and a timing difference between systems takes as long to explain as a genuine error.

Customer service. Customers want to know what they hold, what has moved and what it is costing them. Separate systems mean manual extraction and reports that are out of date on arrival.

Each problem is manageable on its own. At scale, across many customers with goods at different stages, they compound. A billing dispute is rarely one big error. It is usually many small differences between customs events, yard records and the charging terms.

One shared history, multiple controls

The fix is one auditable movement history that customs, yard and finance all draw on, with each item traceable to the declarations behind it.

That history should hold:

1. item details and specifications
2. the customer who owns the goods, and the customer's own batch or purchase order references
3. the HS code and the classification history behind it, including the 12-digit code where a declaration needs one
4. the Bill of Entry under which the goods arrived, linked to the relevant declaration line, and their current customs status
5. quantity with an explicit unit, keeping pipe count, length, weight and package count separate
6. physical location in the warehouse or yard, and handling status
7. actual receipt and release dates, the movement type for each event, and supporting references such as offload sheets
8. the storage charging method in the customer's agreement, and the time on site that feeds it
9. the Bill of Exit when goods depart
10. the documents behind every event, with timestamps and the user who approved them

Link the detail beneath customs summaries

A customs declaration may group goods under the same HS code while the customer tracks them by batch or purchase order. Those separate stock lines still need a traceable link to the declaration. When part of a batch leaves the yard, the record should show which quantity moved, which customer owned it and which stock remains.

Quantity also needs an explicit unit. Pipe count, length, weight and package count should stay separate, with conversions checked before the data feeds a stock report or storage calculation.

Update stock from what was actually handled

A document describes the expected movement. The team on the ground records what actually arrived or left. A shipment can arrive across several truckloads on different days. Each offload needs its own date and received quantity, with shortages, excess or damage recorded against the relevant stock line. That gives the customs team, yard supervisor and customer service team a common account of what has reached the site.

Different views from the same history

The yard supervisor needs physical location and handling status. The customer needs stock by its own references. Customs needs quantities linked to the relevant declarations. Each view can draw on the same movement history while showing only the detail that user needs.

Where AI and people fit

AI handles the repetitive work: extracting and validating data from commercial invoices, packing lists and Bills of Entry, flagging missing or inconsistent information, and updating records once movements are confirmed. Staff still need to record physical handling accurately.

Authorised people handle the judgement calls: approvals, releases, classification questions and anything outside agreed parameters. Each exception reaches them with the evidence attached and a timestamped log of what was decided and when. That is the pattern behind Ripple's approach to customs clearance automation and classification control.

The aim is one version of the numbers, storage statements that show the basis for each charge, and an audit trail built as the work happens.

Pentagon Freight Services at JAFZA

In October 2026, Pentagon Freight Services selected Ripple to run AI customs and warehouse operations across its Jebel Ali Free Zone warehouse and yard (Ripple). Pentagon is a specialist freight forwarding, project logistics and ships agency provider with more than 50 years serving the oil and gas, energy, marine and construction industries. The JAFZA programme builds on Ripple's existing customs work with Pentagon in the UK.

What the programme covers

Under the agreement, Ripple will work across:

• customs documentation processing and customs-entry preparation, extracting and validating data from commercial invoices, packing lists and Bills of Entry
• export documentation, generating outbound commercial invoices and packing lists for user validation before release
• OCTG inventory management, linking pipe specifications, HS codes, customs declarations, customer ownership, yard location and storage history
• warehouse operations, with records updated as goods arrive and depart
• storage statements showing stock, rates and charges for each billing period, for the finance team to use in its invoicing system
• operational reporting, with customer access to their own inventory position planned as a later phase

Ripple works across Pentagon's existing systems, so teams don't rekey data between platforms. Exceptions go to authorised users with timestamped decision logs, and every transaction keeps a complete audit trail.

"Our JAFZA operation manages large volumes of high-value OCTG and oilfield equipment for customers who need accurate, real-time visibility of their stock and customs position. Much of that has relied on manual data entry and spreadsheets. Ripple gives us a single source of truth, faster and more accurate billing, and the capacity to grow volumes without growing headcount at the same rate.

"Just as importantly, our customers will be able to see their inventory whenever they need to, which raises the standard of service we can offer across the region."

Alex Lewis, Area Director Middle East & India, Pentagon Freight Services

Why OCTG raises the bar for the record

Oil country tubular goods (OCTG) and oilfield equipment put every part of the shared history to work. Items are individually specified by grade, weight, length, connection type and heat number, which matters to the customer and to customs classification. They are often handled in bundles, cradles or other packaging, so pieces, length, weight and package count all need tracking separately.

Stock can be spread across several yard blocks and held for long periods for many customers at once. Goods may be re-exported, transferred between customers or released to the mainland, each a different customs event, and storage charges depend on quantities, dates and the agreed charging method.

Why this matters commercially

Joining customs and inventory is as much a commercial decision as a compliance one. Storage statements that show the quantity, dates and charging method behind each line are quicker to produce and easier for customers to check. Visibility of stock is a service customers increasingly expect. And handling more volume without adding headcount at the same rate is what lets a warehouse scale.

A shared history is designed to support:

• storage statements produced from the record, ready for the finance team to invoice
• less manual reconciliation at the end of each billing period
• customer queries answered from the system rather than from spreadsheets
• audit requests met with a timestamped history that already exists
• growth in volume without growing the back office at the same rate

The results depend on accurate recording of physical handling, and on configuring each customer's charging terms correctly.

Who else this applies to

OCTG is Pentagon's context, but the same design questions apply to free-zone operations holding goods for multiple customers across multiple movement types.

• Freight forwarders and customs brokers: managing import, re-export and mainland transfer flows across a wider range of commodities. A forwarder consolidating goods for re-export through JAFZA needs to know which items are ready to ship, which are waiting on documents and which are transferring to another customer. Those are customs and inventory questions at the same time.
• 3PLs and warehouse operators: holding stock for many customers, each with its own customs position and storage agreement, and each needing its own reporting. Storage charges are a main revenue line, so billing disputes hit margin directly.
• Project logistics operators: handling long dwell times, phased arrivals under one project and releases tied to project milestones. Customers need the cumulative customs, storage and location position across the project.

In each case, the manual effort of keeping separate records aligned tends to grow with volume.

What UAE operators should do next

Before choosing systems or workflows, decide whether customs and inventory will share a record. That decision shapes everything else.

Then map where your customs status, warehouse movements and billing triggers diverge today. In many operations the gaps are already known informally. They surface as the reconciliation meeting, the disputed invoice or the customer email nobody can answer quickly.

Ask these questions about your own operation:

• When goods arrive, how many times is the same data entered, and by how many people?
• Can you confirm an item's customs status, ownership and location from one system, right now?
• How long does it take to tell a customer what they have in stock and what it is costing them?
• Does your storage billing reliably apply each customer's charging method to partial releases and mid-month arrivals?
• If customs or a customer asked for the full history of one item, how long would it take to assemble?

For the wider regulatory and documentation context, see Ripple's UAE customs automation guide.

If the answers make you uncomfortable, that is your business case. Book a call with Ripple to talk through UAE customs and warehouse operations, or explore how Ripple fits your use case.

Common questions

Why do free-zone operators often run customs and inventory separately?

Usually because of how the operation grew. Customs teams own declaration workflows and systems, while warehouse teams own a WMS or spreadsheets. The two weren't designed to share data, so the link between them is often manual. The cost tends to show as volumes grow and reconciliation takes longer.

Do JAFZA operators need 12-digit HS codes now?

Not for most free-zone movements yet. Dubai Customs Notice 02/2026 extended acceptance of 8-digit codes until further notice, and Dubai Customs guidance states that shipments destined for free zones stay on 8-digit codes. Goods released from a free zone to the local market fall in a later phase of the 12-digit rollout, so operators should keep classification data ready for both.

Why do inventory records matter to customs control in JAFZA?

Dubai Customs requires free-zone companies holding a customs business code to run an inventory system compatible with its requirements, so inventory can be checked against customs records during an audit. The inventory history therefore needs to stay traceable to the declarations under which goods entered and left.

Does this replace a customs broker?

No. In this model, AI prepares and validates data and maintains the record, while declarations stay with the operator's established channels. The value lies in removing manual data entry and reconciliation around those processes. Human approval stays on every consequential step.

Does Ripple replace existing warehouse or customs systems?

That depends on the project. Ripple typically works alongside the systems an operator already relies on, such as its declaration route and invoicing system, and builds the functionality that is missing. Each project agrees which systems stay and where the new capability fits.

How does AI fit with human approvals?

AI handles the repetitive work: extracting data from commercial documents, validating it, updating records once movements are confirmed and flagging exceptions. Authorised people approve releases, resolve exceptions and make judgement calls. Timestamped decision logs create the audit trail.

Why should storage billing sit with customs and warehouse data?

Storage charges depend on the same events that change stock and customs status, applied through each customer's agreed charging method. Some contracts bill on stock held at a set date; others charge pro rata for time on site. When billing draws on the shared history, each statement line can show the quantity, dates and method behind it.

What types of goods benefit most from a shared customs and inventory record?

High-value goods with detailed specifications benefit most, especially when held for multiple customers and likely to be re-exported, transferred or released to the mainland. OCTG and oilfield equipment are a clear example. The same logic applies to any free-zone operation managing several movement types across a large inventory.

This article is general operational commentary, not legal or professional advice. Regulatory positions described are current as of November 2026 and should be confirmed with the relevant UAE authorities or a qualified adviser.