How to Check Logistics Software Developer Experience (UAE)

To check logistics software developer experience, ask the vendor to explain your workflows in their own words, speak to two clients who run similar operations, and set a small paid design task before you sign. Real experience shows up in how they talk about shipments, warehouses, customs declarations and cash-on-delivery (COD), not in a list of past logos. This guide gives you the questions, the reference prompts and the tests to use in the UAE and Saudi Arabia.

What does real logistics software experience look like?

Real experience means the team has built and supported software for shipment, warehouse or customs work, and can describe what went wrong and how they fixed it. Generic app skills are not the same thing.

Look for these signs:

• They ask about your process before they talk about technology.
• They know the difference between a booking, a shipment, a consignment and an invoice line.
• They have dealt with messy data: wrong addresses, missing weights, duplicate SKUs.
• They can name the local systems your staff use, such as Mirsal 2 at Dubai Customs, Fasah in Saudi Arabia, or ZATCA e-invoicing.
• They talk about support after go-live, not only delivery.

Watch for the opposite: a vendor who shows a polished demo but cannot say who built it, or who sells the same template to a restaurant and a freight forwarder.

Which questions test shipment, warehouse and customs knowledge?

Ask questions that cannot be answered with a sales script. The table below pairs each area with a question, what a good answer sounds like and a warning sign.

Ask for a screen share, not slides. Ask them to walk through one real, anonymised workflow from start to end.

Check the official details they quote

When a vendor states a rule, ask for the source. For example, Dubai Customs describes Mirsal 2 as its paperless electronic clearance system, connected to other entities in Dubai's trade supply chain. Dubai Trade's declaration notices say brokers and consignees need a valid Mirsal 2 Business Code, and that AWB number validation was added to import declarations from 3 September 2021. The same page lists the Digital MAKASA (due number) service under Mirsal II → Declaration → Manage MAKASA.

A vendor with real experience will know details like these or will say, "Let me check the official page." A vendor who invents an answer is a risk. Rules change, so always confirm current requirements with Dubai Customs, Dubai Trade or the relevant Saudi authority.

How do you run a reference check that tells you something?

A useful reference check asks about problems, not praise. Call at least two clients who run a business like yours. Use these prompts:

1. "What did the vendor get wrong in the first three months, and how fast did they fix it?"
2. "Did the vendor understand your process, or did you have to teach them?"
3. "Who do you speak to when something breaks? Is it the same person who built it?"
4. "Did the final cost and timeline match the quote? What changed?"
5. "Did you need Arabic, multi-warehouse, courier or marketplace integrations? How did those go?"
6. "Have you changed your process since launch? How hard was it to change the software?"
7. "Would you hire them again for a harder project?"

Also ask whether the reference is a current client. A reference from a project that ended five years ago says little about today's team.

If the vendor will not give references, ask why. Some clients do require confidentiality. In that case, ask for a call with a former project lead, or for a live walkthrough of the product in use.

What sample-work test should you set?

Set a small, paid design exercise tied to a real problem in your business. It shows how the vendor thinks. A generic coding test does not.

Pick one task:

• Forwarder: "Sketch how an inquiry becomes a quote, a booking, a job file and an invoice. Show where a customs declaration fits."
• Courier or e-commerce seller: "Design the status flow for a COD parcel that is delivered, refused, or returned. Show how the cash is reconciled."
• Importer or trader: "Show how a purchase order, supplier invoice and shipment link together so landed cost is visible."
• Warehouse: "Show how stock is received, put away, picked and counted, with a second warehouse added."

Say a Dubai forwarder handles 40 shipments a week. Ask the vendor to show what happens when three of them are held for documents and one is split across two invoices. A team that has done this before will ask questions about invoicing and customs holds. A team that has not will draw a happy path.

Score the result on three points: did they ask good questions, did they cover exceptions, and could you follow their explanation?

How to check logistics software developer experience step by step

Use this order. It takes about a week of part-time effort and costs little before you commit.

1. Write your three most painful workflows. For example: customs file preparation, COD reconciliation, multi-warehouse stock.
2. Shortlist two or three vendors. Ask each for logistics work they have shipped, with the exact modules involved.
3. Run a one-hour discovery call. Use the table above. Note who asks questions and who only presents.
4. Request a live demo of a similar product. Ask to see error states, reports and the admin screens.
5. Call two references each. Use the seven prompts.
6. Set the paid design task. Fixed scope, fixed fee, two or three working days.
7. Review the contract. Check data ownership, hosting location, hand-over terms, support hours and what is out of scope. Both the UAE and Saudi Arabia have personal data protection laws (PDPL), so check the official pages and ask a lawyer.
8. Compare on a scorecard. Rate each vendor 1 to 5 on workflow knowledge, local systems, references, exception handling, support and price.

What common mistakes should you avoid?

• Buying on price alone. A cheap quote from a team that does not know customs or COD often gets expensive in change requests.
• Accepting a logistics logo as proof. Ask what the vendor actually built for that client.
• Skipping the integration question. Ask which courier, marketplace, accounting or ERP connections they have built, and which version of your ERP they have worked with.
• Ignoring who does the work. The sales lead and the developers are often different people. Meet the developers.
• Leaving Arabic until later. Retrofitting bilingual documents and right-to-left layouts is slower than planning for them.
• Not planning the exit. Ask how you export your data and who owns the code.
• Treating the demo as the product. Demos run on clean data. Ask to try your messy data.

Where does Quickship fit in?

Quickship is a software company in Dubai, and we are a vendor too, so apply this checklist to us. We build logistics and e-commerce modules and take on custom software on a quote basis. We are a technology provider only. We do not ship, store, import or clear goods, so your operations and licences stay with you and your partners. Ask us the same questions in the table and judge the answers the same way.