Odoo Implementation Plan in Jordan 2027: 90 Days, Week by Week

An Odoo implementation plan for a Jordanian SME can fit in about 90 days when the scope stays standard: eight weeks to go live, then 30 days of close follow-up. This guide lays out those 12 weeks for a typical case: an Amman distributor with one legal entity, 12 people who need a login, and the Accounting, Sales, Purchase and Inventory apps. Treat it as a typical plan, not a promise. Payroll for a large workforce, manufacturing, several companies, custom code or data that arrives late will all add weeks.

Plan backwards from the go-live date. Under Article 16 of the General Sales Tax Law, a business registered for the general sales tax files a return for each two-month period, and ISTD sets each registrant's period dates. Go live on the first day of a period, so each return is built from one system. If your periods run January–February, March–April and so on, your candidate dates are 1 January, 1 March, 1 May, 1 July, 1 September and 1 November. Cross out any that land in your busiest season, such as Ramadan and Eid for a retailer, then count eight weeks back: that is day 1.

Four roles make or break the plan:

• Owner: signs off the scope, chairs a 30-minute decision meeting each week and settles disputes between departments within days.
• Key users: one per area (accounts, sales, purchasing and stock, the till). They clean their own data, test and train colleagues, so free them for about a day a week.
• Accountant, in-house or external: maps accounts and taxes, prepares opening balances and signs off the first return.
• Partner: runs the project, configures Odoo, connects JoFotara, migrates data, trains in Arabic and says plainly when a request needs custom code.

Name one person for each role before week 1.

Copy these lines into a spreadsheet and split them on the | character to get four columns. Day 1 falls eight weeks before go-live, and week 9 starts on go-live day, the 1st of the month.

• Week | Goal | Who | Deliverable
• 1 | Scope: processes, users, apps, plan, hosting | Owner, partner | Signed scope, login list, go-live date
• 2 | Gap review: standard, Studio or code | Key users, partner | One decision per gap; a phase-2 list
• 3 | Accounts and taxes mapped; JoFotara account opened | Accountant, owner | Signed mapping; JoFotara login working
• 4 | Customers, suppliers and products cleaned | Key users | Files with Tax ID, country, unit and tax
• 5 | Test imports; JoFotara and the 16% tax set up | Partner, accountant | Clean test database; JoFotara settings saved
• 6 | Sales, purchase, stock and invoicing configured | Partner, key users | Configured test database; change log
• 7 | End-to-end tests; Arabic training for key users | Key users, partner | Signed test scenarios; a one-page Arabic guide per role
• 8 | Parallel run, end-user training, cut-over rehearsal | Everyone | Matching totals; go/no-go decision
• 9 | Go-live; first JoFotara invoices sent one by one | Partner, accountant | Invoices accepted, QR code on each PDF
• 10 | Daily support; first bank reconciliation | Key users, partner | Issue log with an owner per line
• 11 | Opening balances validated; lock date set | Accountant, partner | Agreed trial balance; Lock Everything date
• 12 (to day 90) | First month-end close; project review | Owner, accountant, partner | Month-end reports; phase-2 plan; handover

Two weeks carry most of the risk: week 3, because the company's ISTD login may sit with someone who has left or with an outside accountant, and week 8, the last cheap moment to catch a mistake. If either slips, move go-live to the next tax period rather than cutting the training.

Weeks 1 and 2 are about saying no. List what Odoo must run on day one, and park everything else on a phase-2 list.

• Users: list by name everyone who needs a login, and what each does in the system.
• Apps: replace today's tools first. For the distributor, that is Accounting, Sales, Purchase and Inventory; add Point of Sale only if there is a till.
• Gaps: for every “we need it to…”, write one decision: a standard setting, a Studio field, or custom code with a written reason.

The same choices drive the bill: the number of logins, whether Studio, a second company or an outside system calling Odoo's API moves you to a higher plan, where you host, custom code (it costs again at every upgrade), payroll inside Odoo, and the training and follow-up you buy. Our guide to Odoo cost in Jordan shows how to read each line of a quote in dinars.

Weeks 3 to 5 are data. Odoo's documentation warns that imports are permanent and cannot be undone, so clean first and test every file in a test database.

• Chart of accounts: map your accounts onto the Jordanian chart that Odoo's Jordan localization installs, with its 16%, exempt and 0% export taxes. Your accountant signs the mapping.
• Customers and suppliers: one record per legal entity, with Country and Tax ID filled in, as Odoo's JoFotara integration requires. Merge duplicates on the tax number, not the spelling.
• Products: unit, cost, sales price and the right tax.
• Opening balances: the trial balance at cut-off, what is still due on each open invoice and bill, bank balances and a stock count. Prove them to the fils: if 48 open invoices add up to JOD 37,412.650, receivables in Odoo must show exactly that.

Keep old codes in the External ID column, so a corrected file updates records instead of duplicating them; our Excel-to-Odoo migration guide shows the templates.

Open the JoFotara side in week 3. As of November 2026, ISTD's joining manual has the company open the National Invoicing System from the ISTD website, choose New User and enter its tax number, username and password, then open the National Invoicing tab and create a JoFotara username and password. Its linking manual then covers what Odoo needs: in JoFotara, choose Connect Devices, then New link, enter a username and pick the income source sequence. JoFotara shows a user number and a secret key to copy.

In Odoo's Accounting settings, under Electronic Invoicing (Jordan), enter the Activity Number (the income source sequence), the Secret Key and the Client ID (the user number), and pick your taxpayer type. The company name must match your ISTD registration, and the currency must be JOD. Guard the secret key like a password.

Then the tax. Article 6 of the sales tax law sets the general rate at 16%, and Article 7 zero-rates exports. A JOD 10.000 item carries JOD 1.600 of tax, JOD 11.600 in all. Your accountant confirms which products are exempt or carry special tax. JoFotara rejects negative invoice lines, so a JOD 50.000 discount on a JOD 1,000.000 invoice becomes 5% on each line.

Configure with one rule: a standard setting first, a Studio field second, custom code last.

In week 7, train key users in Arabic, on your own data in the test copy; each user can switch Odoo to Arabic in My Profile once the Arabic language has been added. Week 8 is the parallel run: re-enter one real week of sales, purchases and payments in the test copy, sending nothing to JoFotara, and compare sales, tax, receivables and stock with the old system to the fils.

From go-live day, Odoo is the only system that issues invoices: no new sale goes through the JoFotara portal or the old program. Then follow a 30-day routine:

• Days 1–3: send the first live invoices one by one with Send, then JoFotara (Jordan EDI), and check each is accepted with a QR code on its PDF before any bulk send. Odoo's Jordan documentation shows how to add JoFotara State and JoFotara Error columns to the invoice list.
• Every day: a 15-minute error check and an issue log with an owner per line.
• Weeks 10–11: post the final trial balance once the old month is closed, reconcile the bank, then set the Lock Everything date to the last day of the old period.
• Days 28–30: the first month-end close in Odoo. Keep the old sales tax workbook until the first return built in Odoo matches it.

The 8 risks that delay Odoo projects, and how to avoid each:

• Growing scope: write it down in week 1 and send new ideas to phase 2.
• No decision-maker: the owner chairs the weekly meeting and decides on the spot.
• Key users with no time: free them about a day a week.
• Late, messy data: one owner per file, a week-5 deadline and test imports.
• JoFotara access left to the end: find the company's ISTD login in week 3.
• Old habits rebuilt in code: standard first, Studio second, code last.
• Generic training: in Arabic, on your own data, close to go-live.
• The wrong date: mid-period, in peak season, or with no parallel run.

Our guide to choosing an Odoo partner in Jordan lists the questions to ask before you sign. If you want a second pair of eyes on your own plan, METCH, an official Odoo partner serving Jordan, can review it with you.