Document preparation
- Export file
- Pro formas, commercial invoices and packing lists can be scoped from orders.
- Import file
- Separate templates and fields can be selected for incoming-document checks.
Development on request
Export & Customs OperationsReview shipment documents, stages and late-arriving expenses through a shipment file. We will scope the export and customs software we will build around the checklists used by your foreign-trade team and customs broker.

Find why a file is waiting by identifying its document and responsible person. Separate preparation of pro formas, commercial invoices and packing lists can leave quantity or buyer changes inconsistent. A broker's document may stay in another conversation while logistics assumes the cargo is ready. We will plan shared shipment information linked to a file and missing-document tracking against your checklist. Together, we will choose its source and the person responsible for updates.
Let us examine a sample shipment file. We will start with required documents selected by you and your broker. Stage transitions can account for transport records and document completion progressing independently.
Order details, pro formas and shipment document templates can be considered in one file. Preparation and checking responsibilities can have separate fields.
Container, seal and bill-of-lading numbers can be added. Shared fields for commercial invoices and packing lists can be selected within document preparation scope.
Broker-provided declaration numbers, dates and documents can link to the file. Departure, arrival and expense completion can be separate states; letter-of-credit dates can be tracked separately.
Let us define the starting boundary for trade records. We will discuss how to use templates you maintain for each country. The software we will build will be scoped around daily file tracking and your team's data sources.
If you need both directions, shared expense structures can be retained while documents and stages stay separate. One checklist may not suit every transaction; your trade team and broker determine the template. During discovery, we will choose how direction affects file fields and checking order.
| Compare file requirements for export departures and import arrivals | Export file | Import file |
|---|---|---|
| Document preparation | Pro formas, commercial invoices and packing lists can be scoped from orders. | Separate templates and fields can be selected for incoming-document checks. |
| Stage sequence | Loading, departure and arrival records can be defined. | Arrival and processing stages can follow your team's tracking arrangements. |
| Expense assessment | Shipment expenses can be compared with the sale amount. | File-level expense breakdowns and storage tracking can be selected. |
Working in one file does not require sharing every commercial detail. Broker access to necessary documents differs from access to sale values or company cost summaries. The software we will build can include file-level permissions and document-update histories.
Document preparation, missing-item checks and transport entries can be separated by role. Date-editing rights will be defined separately from stage-status permissions.
A broker can receive access limited to relevant files. Expense entry and financial exports will have permissions separate from external sharing.
KVKK, Turkey's personal data protection law, and retention needs will be considered for buyer and supplier contacts; your firm is the data controller. Customs, trade and fiscal requirements will be scoped following assessments by your broker and authorised advisers.
Consider physical cargo status and document status separately to choose the next action. A loaded container may still lack a document or await broker checks. We will scope missing items, responsible people and delay explanations in the same file. Storage and other waiting costs can link to the shipment. Letter-of-credit dates can also link to it; interpretation of conditions and transaction decisions remain with your bank, broker and authorised team.
First, clarify which shipments remain in progress. Document names alone are insufficient without shipment ownership. Using an anonymised example, we will examine mappings for file numbers, dates and expense sources.
Use checklists verified by you and your broker. Different names for the same document can be mapped; we will choose who keeps the lists current.
Compare document states, stage dates and expenses for one shipment in a sample transfer. Marking fields that cannot transfer can form part of acceptance checks.
If transport or accounting providers offer API access, assess data fields and status codes. File transfers or responsible-person entry can be planned for information without a connection.
Before discussing scope, list information repeatedly sent to brokers, logistics and accounting. These resources can help you discuss shared records for those handovers. Your authorised team will determine documents according to country, goods and transaction type.
Make blank document lists, stage schedules and expense breakdowns suitable for sharing. For letter-of-credit tracking, add the date fields required. A waiting-cargo example can identify who completes which documents and help select first-release checks and records.
The proposal will reflect file types, document preparation, expense detail and assessed connections. Subscription use, support and additional modules will be discussed in the written scope.
We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.
We listen to how your business works, your team and the tools you use today.
Modules, priorities and price are set out in a written quote.
We show working versions at short intervals and move on with your feedback.
We move your existing records across and help your team get started.
We run the software on a subscription and keep it up to date and secure.
No. The declaration is filed by your customs broker through the official system. The software we build manages document preparation, missing items, costs and shipment stages; it does not replace your broker, it helps a complete file reach them.
No. The software checks against the lists that you and your customs broker define. Regulations and bilateral agreements change, and keeping the lists current is your and your broker's responsibility. We do not give advice on customs or foreign trade regulations.
Container status can be updated manually or by file import. Automatic tracking depends on a connection offered by the shipping line or a data provider and often requires a separate subscription; we assess with you during discovery whether you need it.
No. You enter the dates and the list of required documents, and the software counts down and warns you. Interpreting the letter of credit is a job for your bank and advisers. A connection to bank data can only be scoped per project.
The scope can include the import direction. The stage flow and document list are defined separately for imports, and cost breakdowns and storage charge tracking can be designed to work the same way in both directions.
Exporting sales invoices, cost lines and exchange rate differences can be scoped, and e-Invoice flows can also be connected. We discuss which package you use during discovery and tell you from the outset whether a direct connection or a file transfer is possible.
Transport status and financial close can be designed separately. Later freight, storage or brokerage costs can be added to the relevant file and considered in its expense breakdown.
An absent document and an existing document awaiting authorised review can have different states. Discovery will define who marks a document complete and which stage depends on that decision.
After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.
In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.
We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.
Textile & Garment Manufacturing
Software we build on request for textile and garment manufacturers: colour and size breakdowns, stage tracking from cutting to packing, subcontract units, fabric and waste records.
ViewPrint Shop & Commercial Printing
Software we build on request for printers and print shops: quotes, job cards, press and finishing stages, paper consumption, waste and the real cost of every job.
ViewCatering and Central Kitchens
We build software around your kitchen that follows the flow from site headcounts to production orders, and from recipes to allergen and temperature records.
ViewUse document and expense examples to prepare development scope for your firm.