ERP Business Analyst in Jeddah

Forwarders, customs brokers and shipping agents around the port

Jeddah's Red Sea port supports a whole layer of service companies: freight forwarders, customs brokers, shipping agents, transport contractors and warehouse operators. Their business is not buying and selling goods, so a standard trading ERP fits them poorly.

For these firms, the unit of work is the shipment or job. Each job collects revenue from the client and costs from carriers, the port, transporters and government fees. Some of those costs are disbursements paid on the client's behalf and passed through, while others are the firm's own expenses. Profit has to be calculated per job, and unbilled costs must not be forgotten when a file closes.

I document the job lifecycle from quotation through booking, clearance, delivery and final invoice, with the documents that drive each step. Requirements cover how disbursements are recorded and rebilled, how deposits and advances from clients are handled, how a job is closed and how management sees margin by client, trade lane and service type. Some firms are better served by a dedicated forwarding system linked to an accounting platform. The analysis makes that choice visible early. My logistics industry page covers the wider process.

Gold and jewelry traders: weight, purity and making charges

The gold and jewelry shops of Jeddah's older markets and malls run on pricing logic that ordinary retail software does not expect. An item's price depends on its weight, its purity, the day's metal rate and a making charge, with stones and other components priced separately. Customers may trade in old gold against a new purchase, and stock is often counted by weight as well as by piece.

As a business analyst, I document each of these rules with the people who apply them at the counter and in the back office. Requirements cover how the daily rate is entered and approved, how each piece is tagged with weight, purity and cost, how buy-back is valued and recorded, how scrap and melting are tracked and how stock is reconciled by weight.

Tax treatment of precious metals can differ depending on the type of transaction and the parties involved. I do not decide that treatment. I mark each related requirement for confirmation by your tax advisor, so the configuration follows professional advice rather than assumption. Specialist jewelry software exists alongside general ERP platforms, and the requirements make it easier to compare both fairly through an ERP evaluation.

Fabric, abaya and perfume wholesalers: units, variants and leftovers

Jeddah's textile and perfume trades have their own logic. A fabric wholesaler buys rolls by weight or length, sells by the meter to tailors and abaya makers, and ends up with short leftover pieces that are sold cheaply or written off. Abaya producers manage styles in many sizes and colors, often with embroidery or finishing done by outside workshops. Perfume and oud houses buy oils in bulk, blend or decant them and sell the result in bottles of different sizes, sometimes as gift sets.

These businesses need careful requirements for units of measure and conversions, variants and how they are created, partial quantities, simple blending or repacking steps and how cost flows from bulk purchase to finished product. Without that detail, stock figures in the new system drift from reality within weeks of go-live.

I map each flow with the staff who cut, blend or pack, and I write requirements that cover the awkward cases: a roll returned half used, a blend made in a different quantity from the recipe, a gift set broken up for single sales. Those cases go straight into the test scenarios. My wholesale industry page sets out the core wholesale process.

Capturing processes from teams of many nationalities

Warehouses, workshops and shop floors in Jeddah are staffed by people from many countries. The same team might include colleagues more comfortable in Arabic, Urdu, Bengali, Tagalog or English. The people who know a process best are often the ones least comfortable in a long workshop held in a language that is not their own.

The engagement runs in English, so I adapt how requirements are gathered. I rely on visual swimlane maps that show who does what with arrows and document images rather than dense text. Supervisors record short phone videos of a task being done, which I review and turn into draft maps. I keep questions short and concrete, such as what happens when a delivery arrives without paperwork.

Before anything is finalized, a supervisor or bilingual colleague goes through the map with the staff who do the work, in whatever language suits them, and confirms or corrects it. Wherever process text must appear in Arabic or another language, a fluent colleague of the staff concerned drafts or proofs it. This keeps requirements faithful to how work really happens. The approach builds on my ERP process mapping service.

Tying every requirement to a real document

A requirement such as handling partial shipments is easy to agree and easy to misunderstand. In a Jeddah trading or logistics business, the clearest way to remove ambiguity is to link it to the actual paperwork: a bill of lading with several containers, a delivery order released in stages, a cutting slip from the fabric counter or a gold sale receipt showing weight and making charge.

I build an evidence pack of real, anonymized documents from your business. Each requirement in the specification points to the document or transaction that illustrates it. Vendors then demonstrate their system using the same examples, and gaps show up before a contract is signed rather than during testing.

The pack also helps later. Testers use it for acceptance scripts, trainers use it to build exercises, and new staff see what the system is expected to do with the documents they handle daily. National requirements such as e-invoicing are handled on the Saudi Arabia ERP business analyst page. City context is on the Jeddah ERP consultant page, and if you want independent help through selection, the Jeddah freelance ERP consultant page explains how.