An operating system for import and export
Control shipment cost before it reaches the warehouse.
Connect an international buy or sell decision to currency, contract, shipment file, documents, receipt or delivery, cost, and cash in one accountable thread—not a trail of email and spreadsheets.
Current evidence covers the Egypt import cycle and can include ACID and Form 4 data. Export remains a separate design-and-acceptance requirement; no ready NAFEZA, CargoX, or government integration is implied.
International trade
One operating thread per shipment
- 1Trade decision
- 2Finance & documents
- 3Movement & border
- 4Cost & cash
Illustrative operating model; scope and integrations are established per engagement.
Where control leaks
One shipment often carries four competing versions of truth.
The problem is not one missing document. It is the separation of the commercial decision from finance, execution, and accounting.
- 01
Landed cost arrives late
Supplier price, freight, insurance, customs, and charges come together too late to protect margin.
- 02
No clear document owner
Duplicate files, critical dates, and distributed approvals make gaps expensive to discover.
- 03
Currency and cash sit elsewhere
The purchase decision is rarely read beside FX exposure, facilities, LC milestones, and upcoming obligations.
- 04
Handoffs lose context
Imports, warehouse, finance, and sales share a shipment number, but not the reason for an exception or the decision taken.
End-to-end workflow
From international-trade decision to financial closure.
The sequence below follows the import path supported by current evidence. Export is mapped separately from customer order and documents through delivery and collection, with an owner and acceptance rule for every handoff before build.
- 01
Demand and source
Confirm item, quantity, supplier, trade terms, and the reason to buy.
Handoff owner
Commercial & procurement
- 02
Order and terms
Purchase order, currency, payment terms, dates, and expected documents.
Handoff owner
Procurement
- 03
Finance and exposure
LC, transfer, or facility, read beside currency exposure and maturity.
Handoff owner
Treasury & finance
- 04
Shipment file
Documents, responsibilities, milestones, and every missing or conflicting item.
Handoff owner
Import operations
- 05
Arrival and clearance
Clearance data, charges, and exceptions through release.
Handoff owner
Imports & broker
- 06
Receipt and cost
Match receipt, allocate cost, and connect serial or lot identity where scoped.
Handoff owner
Warehouse & finance
- 07
Sale and settlement
Carry cost into price, invoice, collection, and shipment-obligation settlement.
Handoff owner
Sales & finance
The integrated story
A shipment is not managed in one screen, but from one truth.
Value appears when every team keeps its expertise while decisions, documents, and cost share a common reference. An exception then becomes an owned event with impact—not a lost message.
- Commercial decision
- Treasury & finance
- Import file
- Stock & cost
- Sale & collection
Common reference
Connects order, shipment, receipt, and invoice without rebuilding the story.
Exception ownership
Defines who acts, by when, and which evidence closes the state.
Reviewable close
Reconciles quantity, charges, and obligations before cost is approved.
Capabilities grouped by outcome
Scope designed to protect cost, shipment flow, and liquidity.
These are not a fixed bundle. Evidenced import capabilities are selected and accepted per engagement; export remains a separate design-and-acceptance requirement until its scope is proven.
Each item is established in scope and acceptance
Protect cost and margin
Make the buying decision financially legible.
- FX-aware, multi-currency pricing workflow
- Shipment cost structure and charges
- Assumption-to-approved-cost comparison
- Cost impact on the selling decision
Each item is established in scope and acceptance
Control document flow
Know what is missing and who owns it before the critical date.
- Import, LC, and customs workflow
- ACID and Form 4 data in verified Egypt scope
- File responsibilities, dates, and exceptions
- Serial or lot traceability where required
Each item is established in scope and acceptance
Close the operating loop
Connect receipt to inventory, invoicing, and cash.
- Connected purchase, stock, sales, and invoicing cycle
- Treasury, facilities, and post-dated-cheque workflows
- Receipt and charge reconciliation
- Export-order, document, delivery, and collection handoffs as a separate design-and-acceptance requirement
- Arabic outputs when included in scope
Value by role
Each role sees the decision it owns—not another copy of the spreadsheet.
Permissions and views are designed after responsibility and data ownership are settled.
Executive leadership
What do open shipments mean for margin and liquidity?
A view connecting commercial, cash, and execution commitments.
Import manager
Which file is blocked, why, and who owns the next action?
Exceptions tied to document, date, and accountable owner.
Treasury and finance
When is finance due, and which exposure sits behind it?
Obligations read beside the shipment and its cost.
Warehouse and sales
What arrived, and at what cost can we commit?
A common reference from receipt to availability and price.
The measurement story
Measures that explain where shipment cost and time changed.
We show no invented numbers. Definition, source, and decision come first; the engagement establishes the baseline.
Conceptual measurement model—no values or performance promises.
- 1
What is measured
Landed-cost variance
Difference between the buying assumption and approved cost after charges.
Decision supported
Change source, terms, selling price, or margin guardrail.
- 2
What is measured
Clearance cycle time
From the agreed arrival point through release and receipt.
Decision supported
Identify the delay cause and corrective owner.
- 3
What is measured
Document exception rate
Files needing completion or correction under a fixed definition.
Decision supported
Improve the checklist and source responsibility.
- 4
What is measured
Cash-obligation cover
Expected payments read against available cash timing.
Decision supported
Sequence finance and schedule maturities.
Decision scenarios
Start with a transaction that is hard to explain today.
These are analysis starting points, not ready implementation templates.
- 01
Charge-heavy shipment
Trace how charges accumulate and when cost becomes safe for a selling decision.
- 02
FX-sensitive letter of credit
Connect finance terms, exposure, and price instead of treating each file alone.
- 03
Receipt discrepancy
Define how shortage, damage, or document conflict affects stock, cost, and supplier action.
- 04
Export order needing its own path
Map international-sale terms, documents, delivery, and collection as requirements accepted separately from the import cycle.
Egypt operating context
Local boundaries belong in project scope—not in a broad slogan.
International trade in Egypt varies by goods, authority, bank, broker, and contract. The operating design must make those differences explicit.
- An Egypt engagement can include ACID and Form 4 data in the import workflow.
- Any NAFEZA, CargoX, bank, or broker connection needs its own interface, data owner, and acceptance test.
- Export documents, terms, and parties are established as a separate local path; import assumptions are not copied onto it.
- Egyptian e-invoicing enters only after project-specific technical and regulatory verification.
Why GizaLink
Because a shipment file needs process design, not another screen.
We begin with a real transaction, map responsibility and data handoffs, then establish what is built, integrated, and accepted.
Grounded operating depth
Import, LC, and customs workflow in Egypt has project-bound delivery evidence.
One financial and operating view
Pricing, treasury, and the connected core sit around the import file.
Managed delivery
Analysis, blueprint, build, migration, training, and go-live under contractual responsibilities.
Complete the decision picture
Import and export ERP questions
Direct answers before the scenario becomes scope.
Does GizaLink have a ready NAFEZA or CargoX integration?
This page does not imply one. Every external connection requires an agreed interface, data owner, failure responsibility, and acceptance test.
Can the scope manage ACID and Form 4 data?
An Egypt engagement can include import, LC, and customs workflows with ACID and Form 4 data after the company process and documents are confirmed.
How is landed cost handled?
We first define cost components, allocation rules, approval point, and source for every amount; the accepted mechanism is then designed with operations and finance.
Can the workflow handle foreign currencies?
FX-aware, multi-currency pricing workflows can be delivered within engagement scope, with rate sources and approval rules made explicit.
What is the best transaction for discovery?
Use a recently closed shipment with a cost, document, or timing discrepancy. It quickly reveals the real actors, systems, and exceptions.
Is export simply the import flow in reverse?
No. Customer order, international-sale terms, export documents, delivery, and collection are established as a separate path with their own requirements and acceptance; this page does not claim a ready export capability.
Begin with one transaction
Turn a real shipment into an executable operating blueprint.
Bring a recent shipment file—order, finance, documents, charges, receipt, and financial impact. We use it to define scope, questions, and evidence.