ERP Business Analyst in Sharjah

Publishers and printers: titles, consignment and returns

Sharjah has built a real publishing community, helped by a dedicated publishing free zone and one of the region's best-known book fairs. For an ERP analyst, publishing is unusual because the product is not just an item. A single work can exist as a hardback, a paperback, an Arabic edition, an English translation and an e-book, each with its own identifier, price and stock.

The requirements I typically capture for a publisher include:

• How a title record relates to its editions, formats and identifiers such as ISBNs.
• How royalties are calculated for authors, translators and illustrators, and how statements are produced for each.
• How stock sent to bookshops and distributors on consignment is tracked until it is sold, returned or written off.
• How sales at book fairs, including cash and card sales on a temporary stand, are recorded and reconciled.
• How rights income from foreign editions is invoiced and followed up.

Printers have a different set of needs: quoting by specification, job tickets, paper usage and wastage, and outsourced finishing such as binding or lamination. Some Sharjah businesses do both, publishing their own titles and printing for others, and the requirements must keep those two flows apart in costing while sharing customers and stock.

Private schools and training institutes

Sharjah is home to a large number of private schools, nurseries, language centers and professional training institutes, as well as the universities in University City. Many of them run finance on one system and student records on another, connected by spreadsheets that the accounts office reconciles at the start of each term.

When I analyze an education organization, I start by drawing the line between what the school's student information system already does well and what the ERP must handle. The ERP side usually covers fee structures by grade or course, installment plans, sibling and staff discounts, scholarships, transport fees by route, sales of books and uniforms, refunds when a student leaves mid-term, and payroll inputs for teaching staff.

Private education in the emirate is regulated, and schools follow rules on matters such as fee changes and reporting. I do not interpret those rules. I record which reports and approvals the school's management says it needs, and I ask the school to confirm them with its regulator or advisor before they become requirements. The result is a clear specification for the finance side, with integration points to the student system defined in writing. My education industry page covers the sector more broadly, and education ERP in the UAE adds the national context.

Free zone movements in SAIF Zone and Hamriyah

Manufacturers and traders based in SAIF Zone or Hamriyah Free Zone often move goods in several directions: imports arriving through the ports or the airport, finished goods shipped abroad, sales into the UAE mainland, and transfers between a free zone company and a related mainland company. Each movement can involve different paperwork, and the people handling it are often a clearing agent outside the business and one coordinator inside it.

My role as business analyst is not to decide the customs or tax treatment of any movement. That belongs to your clearing agent, the free zone authority and your tax advisor. What I can do is specify the data those people will ask for, so it is already sitting in the system when the shipment moves. In requirements terms, that means specifying:

• Which movement types exist, and what triggers each one.
• Which reference numbers, documents and descriptions must be stored against a shipment.
• How stock is shown while it waits for clearance.
• Which reports the coordinator prepares and who receives them.

Writing these down early avoids a common problem: a system that handles sales and stock well but forces the coordinator to rebuild movement records by hand in a separate spreadsheet. The national compliance angle is covered on my UAE ERP business analyst page.

Ranking requirements by what they cost to build

A requirements document that lists everything everyone wants is easy to write and hard to afford. Sharjah owners in particular tend to ask, quite reasonably, which items are driving the quotation. So every requirement I write is tagged with how it would likely be delivered:

• Standard: the chosen platform does it out of the box with normal setup.
• Configuration: it needs settings, workflows or reports that an implementer builds without code.
• Custom: it needs development, which brings build cost, testing effort and ongoing maintenance.

Alongside that tag I add a short note on what drives the effort, such as an integration with an outside system, a complex approval rule or a document layout that must match a regulator's format. During the review, the owner and department heads go through the custom items one by one and decide whether each belongs in the first phase, a later phase or nowhere.

This turns a long wish list into a scope that matches the budget, and it gives vendors a clearer basis for pricing. It also makes later change requests easier to judge, because everyone can see what was deliberately left out. This approach builds on my ERP gap analysis method.

What the finished Sharjah BRD contains, and how the work runs

The main deliverable is a business requirements document with numbered requirements, current-state process maps, the cost tags described above, sample documents such as invoices, delivery notes, job tickets or fee statements, and a list of open questions with an owner for each. Test scenarios are drafted from the same numbered list, so user acceptance testing later checks exactly what was agreed.

All of this is done remotely. I run interviews by video with each department, usually short sessions that fit around production or teaching schedules, and collect documents through a shared folder. Staff who prefer Arabic can explain their work in Arabic with a bilingual colleague translating; the requirements themselves are written in English, and any Arabic labels or layouts are reviewed by native speakers inside your organization before sign-off.

Where the BRD feeds a platform decision, it moves straight into evaluation and selection. For the operational side of Sharjah ERP projects, see my Sharjah ERP consultant page; for owners who want ongoing independent support rather than a single document, the freelance ERP consultant in Sharjah page explains the options. You can also get in touch to discuss your requirements.