Factories across Africa, the Middle East and Asia
Cold rooms, dairies, packhouses, process plants and stores across those regions. Register the sites where your people are close enough to reach the plant and support it.
Partner programme
Bring FactoraERP IoT to factories you already serve across Africa, the Middle East and Asia. Once accepted, you work in a dedicated partner CRM: register deals, track the pipeline and the deployments, and stay with the IoT.Factora team through hypercare. You register sites your team can reach and support.
Cold rooms, dairies, packhouses, process plants and stores across those regions. Register the sites where your people are close enough to reach the plant and support it.
The differentiator is not another monitoring login. The ERP setting is FactoraERP, another ERP through an integration pack, or none. A plant does not have to replace its system to use the sensors. A reading meets production, maintenance and the batch because it is already in the plant record.
The software fee continues after the install. How that is shared, as a margin or otherwise, is discussed during onboarding. This page does not publish a percentage.
Registered, Certified delivery, Technology alliance, and Strategic. Pick the one that matches the work you already do. The application asks which you want. It does not grant it.
Start by introducing the product to plants you already know. You register the opportunity. You do not have to commission the site yourself.
This track is for the firm that stands in the plant: survey, install, prove the telemetry, train the users, and hand the site over.
Bring a product you already ship: a gateway, a probe family, a panel, or a system a plant already runs. We will say what has been read, and we will not put a logo up before that.
A few firms will cover more than one plant with us: a region, or a sector such as cold chain or dairy. We agree that track. An application does not award it.
Apply, qualify, get enabled, register deals, deliver against the gates, then hypercare and live.
01
Tell us the firm, the track you think fits, the region and countries you cover, and what your people can actually do. The form is the application. It does not open the partner CRM. That workspace comes after you are accepted.
02
We reply and say whether the track fits. Registered, Certified delivery, Technology alliance and Strategic are not the same conversation. A no is a possible answer.
03
Accepted firms get a dedicated partner CRM workspace and meet the product. You use it to register deals, track the pipeline and deployments, and work with the IoT.Factora team. Sales, Delivery and Service certifications use Academy, sandbox labs, and a practical assessment. This site does not publish the CRM address, and it does not print a certificate.
04
In the partner CRM you register the customer, the site, the industry, the use case, an estimated value, the expected close, and who owns it on your side. That is how attribution works. The CRM address is given after acceptance. It is not on this website.
05
A won deal becomes a deployment: scoping, readiness, provisioning, commissioning, then acceptance. The six gates are the checklist. A box on the wall is not acceptance.
06
After acceptance the site sits in hypercare, then live. A deployment can also be blocked or closed. The record keeps the delivery lead, the target date, the device count, the support owner, and the risks.
Partner-originated work stays with the partner who registered it. After acceptance, that registration lives in your partner CRM, with the pipeline and the deployments, and you work it with the IoT.Factora team. The record holds the customer, the site, the industry, the use case, an estimated value, the expected close, and the partner owner. The CRM address is not published here, and the workspace does not open the customer’s plant.
The opportunity is on the record, with the partner who brought it.
We are checking the plant, the use case, and whether the product fits.
A proposal is in front of the customer. It is not a win.
The customer has agreed. Delivery can start. Attribution stays with the partner who registered it.
The customer chose not to proceed. The record stays, so the same plant is not registered twice in confusion.
The registration does not qualify. We say why. It does not become a silent loss.
A deployment moves through Scoping, Readiness, Provisioning, Commissioning, Acceptance, Hypercare, and Live. It can also be blocked or closed. The record names a delivery lead, a target date, a device count, a support owner, and the risks. Naming a support owner is not a ticket desk. These six gates are what “accepted” means.
Gate 1
The rooms, the panels, the power, and the path for the network have been looked at, not assumed from a phone call.
Gate 2
Power, mounting, and the network the gateway needs are actually in place before commissioning starts.
Gate 3
Readings arriving from the site match the points you said you installed. A green icon on a slide does not count.
Gate 4
A known excursion or fault is raised and acknowledged, and the name stored is a person.
Gate 5
The people who will use the floor, the alerts, and the acknowledgement have been shown the product on their own site.
Gate 6
The customer accepts the site against those gates. That is the close of delivery, not the day the carton was opened.
Sales, Delivery and Service are certifications for people, not a badge for the company letterhead. Academy is 25 lessons, about 400 minutes. Onboarding, areas and lines, the sensor registry, and gateways and data sit in setup beside it. The same Academy includes sales and implementation tracks. Enablement adds sandbox labs and a practical assessment. A certificate is not issued automatically, and this site cannot download one for you.
For the person who qualifies a plant and registers a deal. They should be able to say what the product does, and what this site still will not claim.
For the person who surveys, commissions, and walks the six gates. Certified delivery partners need this on the team that goes to site.
For the person who stays with the site after go-live. It is separate from Delivery. Holding one does not imply the other.
You already join panels, software and a plant network. Certified delivery is the usual track.
You pull cable, land a panel, and talk to a PLC. Delivery, once your people are certified.
You fit rooms, packhouses and the probes that watch them. The gates include a tested alert, not only a sensor on the wall.
You already sit with the production and finance system. Registered is the honest start, unless you also install.
You move gateways, probes or panels. Technology alliance if you have a product to name. Registered if you introduce plants and stop there.
The partner CRM is real, and it is issued after acceptance. A few things this page will still not pretend.
Margins, introduction fees and discounts are discussed during onboarding.
Once you are accepted, every partner gets a dedicated partner CRM workspace. You register deals there, track your pipeline and deployments, and work with the IoT.Factora team. This website does not publish the CRM address or a login link. The workspace does not give you delegated access into a customer’s plant. Factory access is issued only to the customer after onboarding.
You register the opportunity in your partner CRM before it is treated as yours. The record holds the customer, the site, the industry, the use case, an estimated value, the expected close, and the partner owner. The stages are registered, qualifying, proposal, won, lost, or rejected. Work that starts with you stays attributed to you. The CRM address is given after acceptance and is not published here.
Six acceptance gates: site survey, site readiness, telemetry verified, alert scenarios tested, user training, and customer acceptance. Around those gates the deployment moves through scoping, readiness, provisioning, commissioning, acceptance, hypercare, and live. It can also be blocked or closed.
They are three separate certifications for people on your team. Enablement is Academy, which is 25 lessons and about 400 minutes, including sales and implementation, plus sandbox labs and a practical assessment. This website does not issue a certificate automatically.
That is discussed during onboarding. This site does not publish a percentage, a rebate, or a price list for partners. The software prices on the pricing page are example fees for a plant, not a partner schedule.
No. Commission is not calculated or paid by an automated system you can log in to. If a commercial term includes an introduction fee or a margin, it is agreed in onboarding and handled with the team. It is not a button on this website.
System integrators, electrical and automation contractors, cold-chain installers, ERP consultants, and hardware distributors who already work with factories in Africa, the Middle East, or Asia. A firm outside that list can still apply. Say what you actually do, and name the countries your team can reach and support.
No. Strategic is a small track we agree with a firm that can carry a territory or a sector. Applying starts the conversation. It does not grant a track, an exclusive, or a logo on this site.
Partners
Tell us the firm, the region and countries you cover, and whether you introduce, install, or sell hardware. We will say which track fits, or that none does yet.