Skip to content

38 terms

Glossary · outsourcing, web, ERP and Tunisian invoicing The words of the trade, defined plainly

This glossary defines the terms that come up when a company or an agency commissions software from ANTASY IT (a.it): delivery and pricing models, business software, Tunisian invoicing rules, the web and the way applications are run. Each definition fits in a few lines and links to the page where we explain how we apply it.

Delivery and pricing models

Delivery and pricing models

How the work is organised, who manages it, and how it is priced.

White-label developmentAlso called: white-label software development

White-label development is a delivery model in which a partner studio designs and builds software that an agency sells under its own brand. The end client deals only with the agency, which keeps the relationship, the contract and the margin.

Where we apply it: White-labelRead the guide: White-label development for agencies

Nearshore development

Nearshore development means outsourcing software work to a team in a nearby country with a similar time zone, so both sides share most of the working day. For Western Europe, Tunisia is nearshore: it stays on UTC+1 all year.

Where we apply it: Nearshore Tunisia

Offshore development

Offshore development means outsourcing software work to a distant country, usually with a large time difference. Work is handed over overnight, which suits well-specified tasks but slows the daily discussions an evolving product needs. Nearshore is the closer alternative.

Where we apply it: Nearshore Tunisia

Staff augmentation

Staff augmentation adds individual developers to your own team, under your management, for as long as you need the skills. You assign the work and run the process; the provider recruits, employs and replaces people. It is usually billed by the month.

Where we apply it: Dedicated team

Dedicated team

A dedicated team is a stable group of developers, often with its own lead, that works only on your product over months. Unlike staff augmentation, the provider organises the team day to day; unlike a fixed-price project, the scope can evolve.

Where we apply it: Dedicated team

Fixed priceAlso called: fixed-scope project

Fixed price is a pricing model in which the price is agreed in advance for a precisely written scope. The provider carries the risk of overruns, and any change of scope becomes a priced amendment. It suits well-defined projects better than products still being discovered.

Where we apply it: Pricing

Time and materialsAlso called: T&M

Time and materials is a pricing model in which the client pays for the hours actually worked, at agreed rates. It suits evolving scopes, where priorities change as the product meets its users. Fixed price suits a scope that is precisely written down in advance.

Where we apply it: Pricing

Requirements specificationAlso called: cahier des charges · specs

A requirements specification describes what software must do: users, processes, documents, business rules, integrations and constraints. A useful one shows real examples, such as invoices, forms and spreadsheets, rather than a feature list. It is the basis of a fixed-price quote and of acceptance testing.

Where we apply it: Process

Minimum viable product (MVP)

A minimum viable product is the smallest version of a product that real users can use to test its key promise. It does the core workflow properly, leaves everything else out, and is built so that it can grow without a rewrite.

Where we apply it: Web apps & SaaS

Handover and reversibilityAlso called: reversibility

Handover is the transfer of everything needed to run software without its original builder: the repository with its history, accounts, credentials, documentation, deployment procedure and data exports. Planned from the start of a project, it lets the client change provider at any time.

Where we apply it: White-labelRead the guide: White-label development for agencies

Business software

Business software

The systems that run sales, stock, production and customer relationships.

ERP (enterprise resource planning)

An ERP is business software that runs a company's core operations on one database: sales, purchasing, stock, production and invoicing. Every department works on the same records, so an order, its delivery, its invoice and its payment stay linked.

Where we apply it: Custom ERP

Custom ERP

A custom ERP is business software developed around one company's own processes, documents and rules, instead of adapting the company to a packaged product. Its code can belong to the company, and the software changes when the way it works changes.

Where we apply it: Custom ERPRead the guide: Custom ERP vs Odoo

CRM (customer relationship management)

A CRM records customers, contacts, opportunities and every interaction, so that a sales team can follow each deal from first contact to payment. Many also handle quotes, customer statements and receivables, which ties the CRM closely to invoicing.

Where we apply it: Custom CRM

Bill of materials (BOM)

A bill of materials lists the components, parts and quantities needed to make or repair one product. Production software uses it to reserve stock, calculate the cost of a job and generate purchasing needs before work starts.

Where we apply it: Production & workshop

Work orderAlso called: repair order · production order

A work order authorises and tracks one job in a workshop or plant: what to make or repair, which materials and parts it consumes, who works on it and its status. Closed orders give the real cost and duration of each job.

Where we apply it: Production & workshop

Serial-number tracking

Serial-number tracking records each unit of a product individually, rather than as a quantity, from receipt to sale, installation, maintenance and repair. It matters for equipment under warranty or periodic inspection, where every unit has its own history.

Where we apply it: Custom ERP

B2B portalAlso called: B2B e-commerce

A B2B portal is an online store reserved for professional customers. Each account sees its own prices, discounts, payment terms and order history, and can reorder quickly. Orders should flow straight into the supplier’s ERP, so nobody retypes them.

Where we apply it: B2B portals

Invoicing in Tunisia

Invoicing in Tunisia

Local rules that shape the data model of any invoicing or ERP software.

Electronic invoice (Tunisia)Also called: e-invoicing

In Tunisia, an electronic invoice is signed electronically by its issuer and registered with Tunisie TradeNet, which assigns it a unique reference. It is mandatory for certain transactions, including the provision of services since 1 January 2026, under the 2026 Finance Law.

Where we apply it: InvoicingRead the guide: E-invoicing in Tunisia (2026)

TTN (Tunisie TradeNet)Also called: El Fatoora

Tunisie TradeNet (TTN) is the body designated by Government Decree n° 2016-1066 to run electronic invoicing in Tunisia. Through its El Fatoora service, it records and stores e-invoices, gives each one a unique reference and sends a copy to the Ministry of Finance.

Where we apply it: InvoicingRead the guide: E-invoicing in Tunisia (2026)

Tax identification number (matricule fiscal)

The matricule fiscal is the tax identification number of a business registered in Tunisia. It appears on its invoices and, when the customer is registered, on the invoices it receives. Made of digits and letters, it deserves a dedicated, validated field in software, never a line of the address.

Where we apply it: Invoicing

Withholding tax (retenue à la source)

Withholding tax is a share of certain payments that the payer deducts and pays to the tax administration on the payee’s behalf. The payer issues a withholding certificate, which the payee uses to offset its own tax, so business software should track every certificate and flag the missing ones.

Where we apply it: Invoicing

Stamp duty (timbre fiscal)

The timbre fiscal is a fixed stamp duty added to invoices in Tunisia, with some exemptions, on top of the total including VAT. Its amount is set by finance law, so invoicing software should hold it as a setting rather than as a constant written into the code.

Where we apply it: Invoicing

Millime

The millime is the subunit of the Tunisian dinar: one dinar equals 1,000 millimes, so amounts carry three decimals, as in 1 571,800 DT. Software must store them exactly, for example as numeric(14,3) in PostgreSQL, never as floating point or with two decimals.

Where we apply it: Invoicing

Bill of exchange (traite)

A traite, or bill of exchange, is a written order by which a seller asks a buyer to pay a fixed amount on a set date. Common in Tunisian trade alongside cheques, it needs tracking by due date, bank and status, from receipt to collection or rejection.

Where we apply it: Custom CRM

Credit note

A credit note cancels or reduces a validated invoice, in whole or in part, after a return, an error or a discount granted afterwards. Sound invoicing software never edits a validated invoice: it corrects it with a credit note, so numbering and VAT totals stay consistent.

Where we apply it: Invoicing

Web, SaaS and e-commerce

Web, SaaS and e-commerce

Kinds of websites and web applications, and how they are built.

Business websiteAlso called: brochure website · site vitrine

A business website presents a company, its services and its contact details, without online sales. Its job is to be found, to convince and to bring enquiries, so speed, clear content and visibility in local search matter more than features.

Where we apply it: Business websites

E-commerce websiteAlso called: online store

An e-commerce website sells products online: catalogue, cart, checkout, payment or cash on delivery, and order management. Behind the storefront, stock, deliveries and invoices must stay in step with the company's back office, or orders end up being retyped.

Where we apply it: E-commerce

Headless CMS

A headless CMS stores and manages content but has no built-in website. It exposes the content through an API, so a separate front end, for example built with Next.js, displays it. Strapi is an open-source headless CMS.

Where we apply it: StrapiRead the guide: Next.js and Strapi 5 in production

Multi-tenant SaaS

A multi-tenant SaaS serves many client organisations from one application and database layer, keeping each tenant's data isolated. One codebase is updated once for all clients. In a single-tenant setup, each client gets its own instance instead.

Where we apply it: Web apps & SaaS

Server-side rendering (SSR)Also called: prerendering

Server-side rendering means the server builds a page's HTML before sending it, so visitors and search engines read the content without waiting for JavaScript. Frameworks such as Next.js combine it with prerendering, which builds pages once, at build time.

Where we apply it: Next.js

Core Web Vitals

Core Web Vitals are Google's three measures of real users' experience of a page: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. Each is measured on real visits and has a “good” threshold set by Google.

Where we apply it: Business websites

Integration and operations

Integration and operations

How systems talk to each other, and how applications are served and kept running.

APIAlso called: REST API

An API (application programming interface) is a documented way for one program to read or change data in another, for example an ERP receiving orders from an online store. A REST API exchanges JSON over HTTP, with access controlled by keys or tokens.

Where we apply it: System integration

Webhook

A webhook is a message that one system sends to another as soon as an event happens, such as a paid order or a new lead, instead of waiting to be asked. The receiving application must verify where it comes from and cope with the same message arriving twice.

Where we apply it: System integration

Biometric time and attendanceAlso called: biometric clocking

Biometric time and attendance uses fingerprint or face-recognition terminals to record when employees arrive and leave. Connected to an HR application, the raw punches become daily presence, lateness, anomalies and hours worked per employee, across one or several sites.

Where we apply it: Biometric attendance

Reverse proxy

A reverse proxy, such as nginx, is the server that receives visitors' requests and forwards them to the applications behind it. It handles HTTPS certificates, domain names, compression and security headers, so that each application can listen privately on its own local port.

Where we apply it: DevOps & hosting

CDN (content delivery network)

A content delivery network, such as Cloudflare, serves a site through servers close to visitors and keeps copies of files in its cache. It speeds up delivery and absorbs attacks, but its cache must follow the origin's Cache-Control headers, or visitors receive outdated pages.

Where we apply it: DevOps & hostingRead the guide: Next.js and Strapi 5 in production

Cache-ControlAlso called: s-maxage · max-age

Cache-Control is the HTTP header that tells browsers and shared caches how long they may reuse a response. max-age applies to browsers, s-maxage to shared caches such as CDNs. HTML that changes with each release should revalidate; hashed static files can be kept for a year.

Where we apply it: DevOps & hostingRead the guide: Next.js and Strapi 5 in production

Staging environmentAlso called: staging

A staging environment is a private copy of an application, filled with test data, where each new version is checked before it goes live. The client tests and approves features there; it should be password-protected and kept out of search engines.

Where we apply it: Process

Go further

A term missing, or a question behind it?

Our guides go into the details with sources, and the FAQ answers the practical questions about working with us.

Prefer to talk it through?

Tell us what you need to build or fix. We answer in English or French, Monday to Friday.