Supply Chain, Inventory, and Logistics Operations

Supply chain management systems track goods from procurement through storage to distribution. These platforms record inventory movements, manage warehouse locations, process requisitions, handle shipments, and maintain stock visibility across multiple facilities. For humanitarian and development organisations, supply chain systems support programme delivery by ensuring commodities reach intended beneficiaries.

This benchmark covers inventory management, warehouse operations, procurement processing, and distribution tracking. It excludes financial accounting (covered in Financial Systems), beneficiary registration (covered in Beneficiary Identity Systems), and cash transfer platforms (covered in CVA Platforms).

Assessment methodology

Tool assessments derive from official vendor documentation, published API references, release notes, and technical specifications as of 2026-01-24. Feature availability varies by product tier, deployment model, and region. Verify current capabilities directly with vendors during procurement. Community-reported information is excluded; only documented features are assessed.

Requirements taxonomy

This taxonomy defines evaluation criteria for supply chain management tools. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations.

Functional requirements

Inventory management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F1.1	Real-time stock visibility	Display current stock levels across all locations with automatic updates on every transaction. Stock quantities reflect actual on-hand inventory without manual reconciliation.	Full: sub-second updates, location-level granularity, API access. Partial: batch updates under 15 minutes. None: manual refresh required.	Create stock movement, verify immediate balance update via UI and API	Essential
F1.2	Multi-warehouse support	Track inventory across multiple physical locations with distinct stock balances per warehouse. Transfer stock between locations with full audit trail.	Full: unlimited warehouses, hierarchical structure, transfer workflows. Partial: limited warehouse count (under 50). None: single warehouse only.	Configure three warehouses, execute inter-warehouse transfer, verify separate balances	Essential
F1.3	Lot and batch tracking	Associate inventory items with lot numbers, batch identifiers, manufacturing dates, and expiration dates. Maintain traceability from receipt through consumption.	Full: mandatory lot capture, expiry alerts, recall support. Partial: optional lot tracking. None: no lot management.	Receive item with lot number, track through transfer and issue, verify complete history	Essential
F1.4	Serial number management	Track individual units by unique serial number for high-value or regulated items. Maintain complete chain of custody per serialised unit.	Full: serial capture at all transactions, warranty tracking, unit history. Partial: serial tracking on selected transactions. None: no serialisation.	Issue serialised item, query unit history showing all movements	Important
F1.5	Stock valuation methods	Calculate inventory value using standard costing methods: FIFO (first in, first out), LIFO (last in, first out), weighted average, or standard cost.	Full: multiple methods selectable per item, real-time valuation. Partial: single method system-wide. None: no automated valuation.	Configure FIFO valuation, process receipts at different costs, verify consumption costing	Important
F1.6	Negative inventory prevention	Block transactions that would reduce stock below zero, or allow with configurable warnings and approvals. Prevent overselling and phantom stock.	Full: configurable per warehouse, approval workflow for exceptions. Partial: system-wide setting only. None: allows negative stock without control.	Attempt to issue more than available, verify rejection or approval requirement	Important
F1.7	Stock reservation	Reserve inventory against specific orders, preventing allocation to other demands. Release reservations on fulfilment or cancellation.	Full: automatic reservation on order, manual reservation, reservation reports. Partial: manual reservation only. None: no reservation capability.	Create sales order, verify stock reserved, attempt to allocate same stock elsewhere	Important
F1.8	Reorder point management	Define minimum stock levels triggering replenishment alerts or automatic purchase requisitions. Configure lead times and safety stock.	Full: automatic requisition generation, demand-based calculation. Partial: alert only, manual ordering. None: no reorder management.	Set reorder point, reduce stock below threshold, verify alert or requisition creation	Important

Warehouse operations

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F2.1	Bin location management	Track stock positions within warehouses using hierarchical location codes (zone, aisle, rack, shelf, bin). Direct put-away and picking operations to specific locations.	Full: unlimited hierarchy levels, location capacity, directed put-away. Partial: single-level bins. None: no bin tracking.	Configure bin structure, receive to specific bin, verify location-level inventory	Important
F2.2	Goods receipt processing	Record incoming inventory from purchases, transfers, or production with quantity verification, quality inspection, and documentation. Generate goods receipt notes.	Full: partial receipt, quality hold, automatic accounting. Partial: full receipt only. None: no structured receipt process.	Receive partial shipment, place portion on quality hold, verify stock and documents	Essential
F2.3	Picking operations	Generate pick lists from orders, direct pickers to stock locations, record picked quantities, and handle substitutions or shortages.	Full: wave picking, zone picking, pick confirmation, shortage handling. Partial: basic pick lists. None: no picking support.	Generate pick list for multi-item order, confirm picks, verify inventory updates	Important
F2.4	Packing and shipping	Record items packed into shipping containers, generate packing lists, and create shipping documentation including labels and manifests.	Full: container tracking, weight/dimension capture, carrier integration. Partial: manual packing records. None: no packing workflow.	Pack order into container, generate shipping documents, verify contents recorded	Important
F2.5	Stock take and cycle counting	Conduct physical inventory counts, compare to system records, investigate variances, and post adjustments. Support full counts and rolling cycle counts.	Full: cycle count scheduling, variance workflow, blind counting. Partial: full count only. None: no structured counting.	Execute cycle count, record variance, verify adjustment posting and audit trail	Essential
F2.6	Quality inspection	Define inspection criteria, record inspection results, manage non-conforming stock, and track disposition (accept, reject, rework).	Full: configurable inspection plans, quality certificates, NCR workflow. Partial: pass/fail inspection. None: no quality management.	Inspect received goods, reject portion, verify quarantine and disposition tracking	Context-dependent
F2.7	Expiry management	Track product expiration dates, generate alerts before expiry, enforce FEFO (first expired, first out) picking, and manage expired stock disposal.	Full: configurable alert periods, FEFO enforcement, disposal workflow. Partial: expiry tracking without FEFO. None: no expiry management.	Receive items with expiry dates, verify FEFO picking sequence, test expiry alerts	Essential

Procurement and ordering

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F3.1	Purchase requisition workflow	Create purchase requests with approval routing based on value thresholds, cost centres, or item categories. Track requisition status through approval.	Full: multi-level approval, delegation, mobile approval. Partial: single-level approval. None: no requisition workflow.	Submit requisition exceeding threshold, verify routing to approver, track status	Important
F3.2	Purchase order management	Create, send, and track purchase orders to suppliers. Support order amendments, partial receipts, and order closure.	Full: order revisions, supplier portal, delivery scheduling. Partial: basic PO creation. None: no PO management.	Create PO, send to supplier, record partial receipt, verify order status	Essential
F3.3	Supplier management	Maintain supplier records including contact details, payment terms, lead times, and performance metrics. Evaluate supplier reliability.	Full: supplier scorecards, qualification tracking, spend analysis. Partial: basic supplier records. None: no supplier database.	Add supplier, record performance data, generate supplier evaluation report	Important
F3.4	Request for quotation	Solicit quotes from multiple suppliers, compare responses, and award orders based on price, quality, and delivery criteria.	Full: RFQ templates, bid comparison, automated award. Partial: manual RFQ tracking. None: no RFQ support.	Create RFQ, enter supplier responses, compare and select winner	Context-dependent
F3.5	Contract management	Record framework agreements with suppliers specifying prices, quantities, and terms. Release orders against contracts and track utilisation.	Full: contract compliance monitoring, price validation, renewal alerts. Partial: contract records without enforcement. None: no contract tracking.	Create contract, release order against contract, verify price enforcement	Context-dependent
F3.6	Demand planning	Forecast future demand based on historical consumption, seasonal patterns, and programme plans. Generate procurement recommendations.	Full: statistical forecasting, scenario planning, demand sensing. Partial: manual forecast entry. None: no demand planning.	Load consumption history, generate forecast, verify accuracy metrics	Important

Distribution and fulfilment

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F4.1	Order management	Create and process orders for distribution to downstream facilities, programmes, or beneficiaries. Track order status from creation through delivery.	Full: order templates, bulk orders, status notifications. Partial: basic order entry. None: no order workflow.	Create distribution order, track through fulfilment, verify status updates	Essential
F4.2	Shipment tracking	Record shipment details including carrier, tracking number, departure and arrival dates. Update order status based on shipment events.	Full: carrier integration, real-time tracking, proof of delivery. Partial: manual shipment recording. None: no shipment tracking.	Create shipment, record transit events, verify order status synchronisation	Important
F4.3	Delivery confirmation	Record receipt of goods at destination with quantity verification and condition notes. Handle discrepancies and claims.	Full: electronic proof of delivery, photo capture, recipient signature. Partial: manual delivery recording. None: no delivery confirmation.	Confirm delivery with signature, report shortage, verify discrepancy workflow	Important
F4.4	Returns processing	Accept returned goods, determine disposition (restock, repair, dispose), and update inventory accordingly. Track return reasons.	Full: return authorisation, inspection workflow, credit processing. Partial: basic return recording. None: no returns management.	Process return, inspect condition, verify inventory update and reason tracking	Context-dependent
F4.5	Kit and assembly management	Define product kits comprising multiple items. Manage kit assembly, disassembly, and component availability.	Full: dynamic kit pricing, component reservation, assembly workflow. Partial: static kit definitions. None: no kit support.	Define kit, assemble from components, verify component consumption	Context-dependent
F4.6	Consignment inventory	Track inventory owned by suppliers but held at organisation locations. Manage consumption reporting and replenishment.	Full: consignment workflows, consumption invoicing, supplier visibility. Partial: separate consignment tracking. None: no consignment support.	Set up consignment stock, record consumption, verify supplier notification	Context-dependent

Technical requirements

Deployment and hosting

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T1.1	Self-hosted deployment	Deploy on organisation-controlled infrastructure for data sovereignty, compliance, or cost management. Full feature parity with hosted versions.	Full: documented deployment, feature parity, supported configuration. Partial: self-hosted with limitations. None: SaaS only.	Review deployment documentation, compare feature matrix	Important
T1.2	Cloud deployment options	Vendor-managed cloud hosting with regional data centre options supporting data residency requirements.	Full: multiple regions including EU, documented data location. Partial: limited regions. None: single region or undisclosed.	Verify available regions, confirm data residency documentation	Important
T1.3	Container deployment	Official Docker images and Kubernetes configurations for consistent, scalable deployment.	Full: official images, Helm charts, orchestration docs. Partial: community images. None: no container support.	Deploy using official containers, verify documentation completeness	Desirable
T1.4	Offline operation	Function without internet connectivity for field locations. Synchronise data when connectivity is available.	Full: complete offline operation, conflict resolution. Partial: read-only offline. None: requires continuous connectivity.	Disconnect from network, perform transactions, reconnect and verify sync	Essential
T1.5	Mobile device support	Native or responsive mobile interface for warehouse operations including barcode scanning and transaction recording.	Full: native apps, offline capable, scanner integration. Partial: responsive web only. None: desktop only.	Test mobile interface, perform scan-based transaction	Important

Scalability and performance

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T2.1	Transaction volume capacity	Handle expected transaction volumes without degradation. Document throughput limits and scaling guidance.	Full: published benchmarks exceeding 10,000 transactions per hour. Partial: undocumented but adequate. None: known limitations.	Review performance documentation, load test if possible	Important
T2.2	Product catalogue scale	Support required number of products and variants without performance impact.	Full: documented support for over 100,000 items. Partial: 10,000-100,000 items. Limited: under 10,000 items.	Review documentation, test with representative catalogue size	Important
T2.3	Concurrent user support	Support expected number of simultaneous users including warehouse staff and administrators.	Full: documented support for over 500 concurrent users. Partial: 100-500 users. Limited: under 100 users.	Review documentation, verify licensing model	Important
T2.4	Data retention capacity	Store historical transactions for required retention periods (5-10 years) without archiving or performance loss.	Full: unlimited retention, archival options. Partial: retention limits with archiving. None: forced data deletion.	Review data management documentation	Important

Integration architecture

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T3.1	REST API coverage	Comprehensive API enabling programmatic access to all major functions for integration and automation.	Full: documented API covering 90%+ of features, versioned. Partial: limited API coverage. None: no API.	Review API documentation, compare to UI features	Essential
T3.2	API authentication	Secure API access using industry-standard authentication methods.	Support for: OAuth 2.0, API keys, service accounts. Document supported methods.	Review security documentation, test authentication	Important
T3.3	Webhook notifications	Push event notifications to external systems for real-time integration without polling.	Full: configurable events, retry logic, payload customisation. Partial: limited events. None: no webhooks.	Configure webhook, trigger event, verify delivery	Important
T3.4	Bulk data operations	Import and export large datasets efficiently for migration and reporting.	Full: async bulk operations, streaming, over 100,000 records. Partial: batch limits under 10,000. None: record-by-record only.	Test bulk import with 50,000 records, measure duration	Important
T3.5	Barcode and RFID support	Generate and scan barcodes (1D and 2D) and RFID tags for item identification.	Full: multiple formats, label printing, scanner integration. Partial: basic barcode support. None: manual entry only.	Generate barcode, scan with hardware, verify recognition	Important
T3.6	ERP integration	Pre-built connectors or documented patterns for integrating with ERP systems for financial and operational data.	Full: certified connectors, real-time sync. Partial: file-based integration. None: custom development required.	Review integration documentation, verify supported ERPs	Context-dependent

Security requirements

Authentication and access control

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S1.1	Multi-factor authentication	Require second authentication factor beyond password. Support multiple MFA methods.	Full: TOTP, WebAuthn, push notification options. Partial: single MFA method. None: password only.	Configure MFA, test authentication flow	Essential
S1.2	Single sign-on integration	Federate authentication with organisational identity providers using standard protocols.	Full: SAML 2.0 and OIDC, multiple IdPs. Partial: single protocol. None: local authentication only.	Configure SSO with test IdP, verify authentication	Essential
S1.3	Role-based access control	Assign permissions based on roles controlling access to functions, warehouses, and data.	Full: granular permissions, warehouse-level restrictions, custom roles. Partial: predefined roles only. None: minimal access control.	Create restricted role, verify access boundaries	Essential
S1.4	Segregation of duties	Enforce separation between incompatible functions (requisition and approval, receipt and accounting).	Full: configurable segregation rules, violation prevention. Partial: warning only. None: no segregation support.	Configure segregation rule, attempt violation, verify prevention	Important

Data protection

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S2.1	Encryption at rest	Encrypt stored data using AES-256 or equivalent to protect against physical media compromise.	Full: AES-256, key management, field-level options. Partial: database encryption only. None: unencrypted storage.	Review security documentation, verify encryption configuration	Essential
S2.2	Encryption in transit	Encrypt all network communications using TLS 1.2 or higher.	Full: TLS 1.3 support, certificate management. Partial: TLS 1.2 only. None: unencrypted options exist.	Verify TLS configuration, test connection security	Essential
S2.3	Audit trail	Record all data changes with user, timestamp, previous value, and new value. Prevent audit log modification.	Full: comprehensive audit, immutable logs, retention controls. Partial: limited audit scope. None: no audit trail.	Make change, verify audit record completeness and immutability	Essential
S2.4	Data masking	Mask sensitive data for non-privileged users while maintaining referential integrity.	Full: configurable masking rules, role-based visibility. Partial: all-or-nothing masking. None: no masking.	Configure masking, verify display for different roles	Context-dependent

Compliance and certifications

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S3.1	SOC 2 certification	Independent audit confirming security, availability, and confidentiality controls (for cloud-hosted solutions).	Full: current SOC 2 Type II report. Partial: SOC 2 Type I. None: no SOC certification.	Request SOC 2 report, verify current validity	Important
S3.2	GDPR compliance features	Tools supporting GDPR obligations: data subject access, erasure, portability, and consent management.	Full: built-in GDPR tools, data processing agreements. Partial: manual GDPR processes. None: no GDPR support.	Test data export for subject access request	Important
S3.3	Pharmaceutical compliance	Features supporting regulated pharmaceutical supply chains: GDP, serialisation, temperature monitoring.	Full: GDP-compliant workflows, serialisation, cold chain. Partial: basic lot tracking. None: no pharmaceutical features.	Review compliance documentation for pharmaceutical regulations	Context-dependent

Operational requirements

Administration

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O1.1	User management	Create, modify, and deactivate user accounts with appropriate access rights. Support bulk user operations.	Full: self-service, bulk provisioning, automated lifecycle. Partial: admin-only management. None: limited user management.	Create user, modify permissions, deactivate, verify access changes	Essential
O1.2	Configuration management	Modify system behaviour through configuration without code changes. Export and import configurations.	Full: extensive configuration, version control, environment promotion. Partial: limited settings. None: requires code changes.	Change configuration, export settings, import to test environment	Important
O1.3	Multi-language support	Interface and reports available in multiple languages. Support right-to-left scripts where needed.	Full: interface, reports, and data in multiple languages. Partial: interface only. None: single language.	Switch language, verify interface and report translation	Important
O1.4	Multi-currency support	Handle transactions in multiple currencies with exchange rate management and conversion.	Full: unlimited currencies, rate history, automatic conversion. Partial: limited currencies. None: single currency.	Configure currencies, process transaction with conversion	Important

Reporting and analytics

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O2.1	Standard reports	Pre-built reports covering common operational needs: stock status, movements, valuations, orders.	Full: comprehensive report library, scheduling, distribution. Partial: basic reports. None: minimal reporting.	Generate stock status report, verify accuracy and format	Essential
O2.2	Custom report builder	Create custom reports without programming using visual tools.	Full: drag-and-drop builder, calculations, parameters. Partial: template modification. None: development required.	Build custom report combining multiple data sources	Important
O2.3	Dashboard visualisation	Visual dashboards showing key metrics with drill-down capability.	Full: configurable dashboards, real-time updates, alerts. Partial: static dashboards. None: no visualisation.	Configure dashboard with KPIs, verify real-time updates	Important
O2.4	Data export	Export data in standard formats for external analysis and reporting.	Full: multiple formats (CSV, Excel, JSON), scheduled exports. Partial: limited formats. None: no bulk export.	Export transaction data to CSV, verify completeness	Essential

Support and maintenance

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O3.1	Documentation quality	Comprehensive, current documentation covering installation, configuration, and usage.	Full: complete user and admin guides, API docs, tutorials. Partial: basic documentation. None: inadequate documentation.	Review documentation coverage, verify accuracy against current version	Essential
O3.2	Vendor support availability	Access to vendor or community support for issue resolution.	Full: 24/7 support, defined SLAs, regional coverage. Partial: business hours support. None: community only.	Review support options, verify SLA terms	Important
O3.3	Update frequency	Regular updates providing security patches, bug fixes, and enhancements.	Full: monthly patches, quarterly features, predictable schedule. Partial: irregular updates. None: infrequent or ceased development.	Review release history for past 12 months	Important
O3.4	Training resources	Materials supporting user training and adoption.	Full: video tutorials, certification programmes, instructor materials. Partial: basic documentation. None: no training resources.	Review available training materials	Desirable

Data management requirements

Import and migration

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
D1.1	Data import tools	Import master data and transactions from files or external systems.	Full: mapping tools, validation, error handling, scheduling. Partial: basic file import. None: manual entry only.	Import product catalogue from CSV, verify data and error handling	Essential
D1.2	Migration utilities	Tools supporting migration from other systems with data transformation and validation.	Full: migration wizards, transformation, parallel operation. Partial: basic import only. None: custom development required.	Review migration documentation for supported source systems	Important
D1.3	Opening balance import	Load initial inventory balances for new implementations without affecting transaction history integrity.	Full: opening balance transactions, valuation support. Partial: manual adjustments. None: no clean starting point.	Import opening balances, verify stock and valuation	Essential

Export and portability

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
D2.1	Full data export	Export all organisation data in portable formats for backup or migration.	Full: complete export including configuration, standard formats. Partial: data only. None: limited export.	Export complete dataset, verify all data types included	Essential
D2.2	API-based extraction	Programmatic access to all data for integration with analytics or other systems.	Full: comprehensive read API, pagination, filtering. Partial: limited data access. None: no extraction API.	Extract transaction history via API, verify completeness	Important
D2.3	Report data export	Export report data to files or external systems for further analysis.	Full: multiple formats, scheduled delivery, parameter passing. Partial: manual export. None: screen viewing only.	Export report to Excel, verify data integrity	Important

Data lifecycle

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
D3.1	Data retention policies	Configure retention periods for different data types with automated archival or deletion.	Full: configurable policies, legal hold, automated enforcement. Partial: manual archival. None: no lifecycle management.	Configure retention policy, verify enforcement	Important
D3.2	Archive and purge	Move historical data to archive storage while maintaining referential integrity. Purge data meeting retention requirements.	Full: selective archival, restore capability, purge with audit. Partial: full backup only. None: no archival.	Archive old transactions, verify accessibility and restoration	Important

Comparison matrices

Rating scale

Symbol	Meaning
●	Full support: feature is complete and production-ready
◐	Partial support: feature exists with limitations
○	Minimal support: basic capability only
✗	Not supported
-	Not applicable to this product category
?	Unable to assess from available documentation

Additional notation:

$ indicates feature requires paid tier
E indicates enterprise edition only
P indicates plugin or extension required
C indicates community-contributed (not vendor-supported)

Functional capability matrix

Inventory management capabilities

Capability	OpenLMIS	OpenBoxes	ERPNext	Tryton	Dynamics 365 SCM	SAP Business One
Real-time stock visibility	●	●	●	●	●	●
Multi-warehouse support	●	●	●	●	●	●
Lot and batch tracking	●	●	●	●	●	●
Serial number management	○	●	●	●	●	●
Stock valuation (FIFO)	◐	◐	●	●	●	●
Stock valuation (weighted avg)	◐	◐	●	●	●	●
Stock valuation (standard cost)	✗	✗	●	●	●	●
Negative inventory prevention	●	●	●	●	●	●
Stock reservation	●	○	●	●	●	●
Reorder point management	●	●	●	●	●	●
Expiry date tracking	●	●	●	●	●	●

Assessment notes:

OpenLMIS provides stock valuation primarily for health commodity costing rather than full financial accounting integration. The platform focuses on quantity management with basic cost tracking.

OpenBoxes implements FIFO for pharmaceutical management. Weighted average and standard costing are not native features, reflecting the product’s healthcare supply chain focus rather than manufacturing cost accounting.

Warehouse operations capabilities

Capability	OpenLMIS	OpenBoxes	ERPNext	Tryton	Dynamics 365 SCM	SAP Business One
Bin location management	✗	●	●	●	●	●
Goods receipt processing	●	●	●	●	●	●
Pick list generation	◐	●	●	●	●	●
Wave picking	✗	✗	○	○	●	◐
Packing and shipping	○	●	●	●	●	●
Stock take / cycle counting	●	●	●	●	●	●
Quality inspection	○	◐	●	◐	●	◐
FEFO picking enforcement	●	●	●	●	●	●

Assessment notes:

OpenLMIS does not implement bin location management as the platform targets health facility logistics where bin-level tracking is less critical than lot and expiry management.

Wave picking (grouping multiple orders for efficient picking) is a feature primarily found in high-volume commercial warehouse systems. Dynamics 365 SCM provides the most comprehensive wave management among assessed tools.

Procurement capabilities

Capability	OpenLMIS	OpenBoxes	ERPNext	Tryton	Dynamics 365 SCM	SAP Business One
Purchase requisition workflow	●	◐	●	●	●	◐
Purchase order management	◐	●	●	●	●	●
Supplier management	○	●	●	●	●	●
Request for quotation	○	○	●	●	●	●
Contract management	✗	✗	◐	◐	●	◐
Demand forecasting	○	●	●P	●P	●	●$

Assessment notes:

OpenLMIS implements requisition-based ordering optimised for health supply chains with approval hierarchies. Full commercial procurement (RFQ, contracts) is outside the platform’s scope.

ERPNext and Tryton require additional modules for advanced demand forecasting. The base stock modules provide reorder point functionality but not statistical forecasting.

Distribution capabilities

Capability	OpenLMIS	OpenBoxes	ERPNext	Tryton	Dynamics 365 SCM	SAP Business One
Order management	●	●	●	●	●	●
Shipment tracking	●	●	●	●	●	●
Proof of delivery	●	●	●	●	●	●
Returns processing	○	●	●	●	●	●
Kit management	✗	●	●	●	●	●
Consignment inventory	✗	✗	◐	◐	●	◐

Technical capability matrix

Deployment options

Platform	Self-hosted	Cloud SaaS	Docker	Kubernetes	Offline capable
OpenLMIS	●	●C	●	●	●
OpenBoxes	●	●	●	◐	◐
ERPNext	●	●	●	●	○
Tryton	●	●C	●	◐	○
Dynamics 365 SCM	✗	●	-	-	◐
SAP Business One	●	●	✗	✗	○

Assessment notes:

OpenLMIS provides Docker Compose and reference Kubernetes deployments. Cloud hosting is available through implementation partners rather than a central vendor SaaS offering.

Dynamics 365 SCM operates as cloud-only SaaS. The Warehouse Management mobile app provides offline capability for warehouse operations but the core system requires connectivity.

SAP Business One offers on-premises and SAP cloud deployment but does not provide official container images.

API and integration

Platform	REST API	GraphQL	Webhooks	Bulk operations	Barcode support
OpenLMIS	●	✗	○	●	●P
OpenBoxes	●	✗	○	◐	●
ERPNext	●	✗	●	●	●
Tryton	●	✗	○	●	●
Dynamics 365 SCM	●	✗	●	●	●
SAP Business One	●	✗	◐	●	●

API coverage details:

Platform	API documentation URL	Authentication methods
OpenLMIS	https://openlmis.readthedocs.io/en/latest/components/	OAuth 2.0
OpenBoxes	https://docs.openboxes.com/en/develop/api-guide/	Session-based, API keys
ERPNext	https://docs.erpnext.com/	API keys, OAuth 2.0, token-based
Tryton	https://docs.tryton.org/	Session-based
Dynamics 365 SCM	https://learn.microsoft.com/en-us/dynamics365/supply-chain/	OAuth 2.0 (Azure AD)
SAP Business One	https://help.sap.com/docs/SAP_BUSINESS_ONE	API keys, session-based

Security capability matrix

Authentication methods

Platform	Local auth	SAML 2.0	OIDC	LDAP/AD	MFA support
OpenLMIS	●	◐	◐	○	◐
OpenBoxes	●	○	○	●	○
ERPNext	●	●P	●P	●P	●
Tryton	●	○	○	●P	○
Dynamics 365 SCM	●	●	●	●	●
SAP Business One	●	●E	○	●	●E

Assessment notes:

ERPNext SSO capabilities require the Social Login Key or LDAP module configuration. Native TOTP-based MFA is available in the base product.

OpenLMIS supports external identity provider integration but requires implementation-specific configuration. The reference distribution includes OAuth 2.0 authentication service.

Data protection features

Platform	Encryption at rest	Encryption in transit	Audit trail	Field-level security
OpenLMIS	◐	●	●	◐
OpenBoxes	◐	●	●	○
ERPNext	●	●	●	●
Tryton	◐	●	●	●
Dynamics 365 SCM	●	●	●	●
SAP Business One	●	●	●	●

Assessment notes:

OpenLMIS and OpenBoxes rely on database-level encryption rather than application-level encryption at rest. TLS encryption protects data in transit.

Commercial comparison matrix

Licensing models

Platform	Licence type	Self-hosted cost	Cloud cost model
OpenLMIS	AGPL v3	Free (infrastructure costs apply)	Implementation partner pricing
OpenBoxes	Eclipse Public License 1.0	Free (infrastructure costs apply)	Hosted service available
ERPNext	GPL v3	Free (infrastructure costs apply)	Per-site from $14/month
Tryton	GPL v3	Free (infrastructure costs apply)	Partner hosting available
Dynamics 365 SCM	Proprietary	Not available	Per-user from $180/month
SAP Business One	Proprietary	Named user licences	Named user licences

Pricing notes:

ERPNext cloud pricing starts at $14/site/month for the Frappe Cloud basic tier. Professional tiers and additional modules increase costs.

Dynamics 365 Supply Chain Management licences at $180/user/month for full users. Additional users (limited functionality) available at $30/user/month.

SAP Business One pricing varies by region and partner. Typical per-user licence costs range from $1,500-$3,000 initial plus annual maintenance.

Nonprofit programmes

Platform	Nonprofit discount	Application process	Restrictions
OpenLMIS	N/A (open source)	-	None
OpenBoxes	N/A (open source)	-	None
ERPNext	N/A (open source)	-	None
Tryton	N/A (open source)	-	None
Dynamics 365 SCM	Up to 75% via Microsoft Nonprofits	Tech Soup or direct Microsoft	Qualifying 501(c)(3) or equivalent
SAP Business One	Partner-specific discounts	Through SAP partners	Varies by partner

Vendor and jurisdictional details

Platform	Vendor headquarters	Data residency options	CLOUD Act exposure
OpenLMIS	VillageReach (USA)	Self-hosted: any location	Self-hosted: none. Partner cloud: varies
OpenBoxes	Partners In Health (USA)	Self-hosted: any location. Cloud: varies	Self-hosted: none. Cloud: verify with provider
ERPNext	Frappe Technologies (India)	Self-hosted: any location. Frappe Cloud: limited regions	Self-hosted: none. Frappe Cloud: verify region
Tryton	Tryton Foundation (Belgium)	Self-hosted: any location	Self-hosted: none
Dynamics 365 SCM	Microsoft (USA)	Azure regions including EU	Yes (US-headquartered provider)
SAP Business One	SAP SE (Germany)	On-premises: any. SAP cloud: SAP regions	On-premises: none. SAP cloud: EU option available

Jurisdictional notes:

Organisations handling protection-sensitive data or operating in contexts where US government data access poses risks should consider data residency implications. Self-hosted open-source options eliminate jurisdictional concerns for application data.

Tool assessments

OpenLMIS

Type: Open-source logistics management information system Licence: AGPL v3 Current version: 3.19.1 (April 2025) Deployment: Self-hosted, Docker, Kubernetes Source: https://github.com/OpenLMIS Documentation: https://docs.openlmis.org

Overview

OpenLMIS is an electronic logistics management information system designed for health commodity supply chains in low- and middle-income countries. The platform manages requisition-based ordering, stock management, and distribution across health facility hierarchies. Originally developed by VillageReach for vaccine supply chains in Mozambique (2010), OpenLMIS now operates in multiple countries including Benin, Côte d’Ivoire, Guinea, Malawi, Tanzania, and Zambia, managing logistics for over 11,000 health facilities.

The architecture follows a microservices pattern with independent services handling authentication, reference data, requisitions, stock management, fulfilment, and cold chain equipment tracking. Each service exposes RESTful APIs documented using RAML specifications. The Reference UI provides a web-based interface consuming these APIs, while the architecture supports integration with external systems including DHIS2 and facility registries via FHIR.

Capability assessment

OpenLMIS excels at requisition-based ordering where facilities request supplies based on consumption and stock levels. The requisition workflow includes configurable templates defining which data elements to capture, approval hierarchies, and supervisory node structures matching health system administrative levels. Stock management tracks quantities by lot number and expiry date, critical for managing pharmaceuticals and vaccines.

The platform handles multi-level distribution from central warehouses through regional depots to health facilities. Proof of delivery confirms receipt at destination facilities. Cold chain equipment management tracks refrigerator inventory and functional status for vaccine storage. Reporting includes stock status, requisition performance, and consumption analytics.

Limitations include the health-sector focus that makes the platform less suitable for general commercial supply chains. Bin location management, advanced warehouse operations (wave picking, packing stations), and manufacturing features are absent. Financial integration is limited compared to full ERP systems.

Key strengths

Health supply chain specialisation: Purpose-built for health commodity logistics with requisition templates, approval workflows, and reporting aligned with public health supply chain requirements.

Offline capability: The mobile application supports offline data collection and synchronisation, essential for health facilities with intermittent connectivity.

Interoperability: FHIR support enables integration with health facility registries. The architecture supports connections to DHIS2 and other health information systems.

Active community: Maintained by a consortium of implementing partners with regular releases, community governance, and shared development costs across implementers.

Key limitations

Sector-specific design: The health commodity focus means general warehouse management features common in commercial systems are absent.

Implementation complexity: Microservices architecture requires container orchestration skills. No turnkey cloud offering exists; implementations require technical partners.

Limited financial integration: Stock valuation and accounting integration are basic compared to ERP-embedded supply chain modules.

Learning curve: The requisition-based model differs from commercial order management, requiring training for users familiar with other systems.

Deployment and operations

Self-hosted requirements:

Component	Minimum specification
Compute	4 CPU cores, 16 GB RAM (reference distribution)
Database	PostgreSQL 12+
Container runtime	Docker 20+ with Docker Compose or Kubernetes
Storage	100 GB (varies with transaction volume)

Deployment complexity: Moderate-high. Requires familiarity with Docker Compose or Kubernetes. Reference distribution provides starting configuration. Production deployments require infrastructure planning, backup configuration, and monitoring setup.

Operational overhead: Regular maintenance includes database backups, security updates, and performance monitoring. The microservices architecture means multiple services to monitor. VillageReach and community partners provide documentation and support forums.

Integration capabilities

Integration type	Support level	Notes
REST API	●	Comprehensive API per service with RAML documentation
Authentication	OAuth 2.0	Token-based authentication via Auth Service
FHIR	◐	HAPI FHIR service for facility data synchronisation
DHIS2	◐	Configurable integration for health data exchange
Webhooks	○	Limited event notification support

Security assessment

OpenLMIS implements OAuth 2.0 authentication through its Auth Service. Role-based access control restricts users to assigned facilities and programmes. Audit logging tracks data changes across services.

The AGPL licence requires disclosure of modifications for hosted deployments, which may affect some commercial implementation models. Security updates follow the community release cycle.

Cost analysis

Direct costs:

Cost category	Self-hosted estimate
Software licence	$0
Infrastructure (cloud)	$200-500/month for reference deployment
Implementation partner	$50,000-200,000+ depending on scope
Annual support	Varies by partner agreement

Infrastructure costs by scale:

Scale	Monthly cloud cost estimate
Small (10 facilities, 5 users)	$150-250
Medium (100 facilities, 50 users)	$400-600
Large (1,000+ facilities, 200+ users)	$1,000-2,500+

Hidden costs: Implementation services represent the primary cost for most deployments. Data migration, customisation, training, and ongoing support typically exceed infrastructure costs.

Organisational fit

Best suited for:

Public health supply chain management organisations
Ministries of health managing pharmaceutical logistics
NGOs implementing health supply chain improvements
Organisations requiring offline-capable stock management

Less suitable for:

Commercial retail or manufacturing operations
Organisations needing integrated financial accounting
Small organisations without technical implementation capacity
General warehouse management without health commodity focus

OpenBoxes

Type: Open-source supply chain management system Licence: Eclipse Public License 1.0 Current version: 0.9.x (active development, January 2026) Deployment: Self-hosted, Docker, managed hosting available Source: https://github.com/openboxes/openboxes Documentation: https://docs.openboxes.com

Overview

OpenBoxes is a supply chain management system designed for managing inventory and stock movements in healthcare facilities and disaster response operations. Partners In Health developed the platform following the 2010 Haiti earthquake to manage emergency medical supplies. The system now operates in multiple countries including Sierra Leone, Lesotho, Rwanda, Liberia, and the United States.

Built on the Grails framework (Groovy/Java), OpenBoxes provides comprehensive inventory management including lot tracking, expiry management, multi-location support, and demand forecasting based on consumption history. The web-based interface supports both desktop and tablet use for warehouse operations.

Capability assessment

OpenBoxes provides full inventory lifecycle management from receipt through storage to distribution. Stock movements track quantities by lot number and expiration date with complete audit trails. The platform supports multiple warehouse locations with inter-warehouse transfers. Bin location management enables precise tracking within warehouses.

Order management handles inbound (purchase orders) and outbound (stock requests, shipments) workflows. Pick lists guide warehouse staff through order fulfilment. Packing records container contents for shipment. Proof of delivery confirms receipt at destination.

Demand forecasting analyses consumption patterns to predict future needs and recommend reorder quantities. The stocklist feature defines standard inventory levels for facility types, simplifying requisition creation.

Key strengths

Healthcare supply chain focus: Purpose-built for pharmaceutical and medical supply management with FEFO picking, expiry alerts, and recall tracking.

Complete inventory management: Comprehensive lot tracking, bin locations, stock movements, and audit trails in a single integrated system.

Consumption-based forecasting: Analyses historical usage to predict demand and optimize inventory levels.

Active development: Regular releases with feature additions and bug fixes. Partners In Health continues active investment.

Key limitations

Limited ERP integration: Financial accounting, HR, and other business functions require separate systems and integration.

Single-tenant architecture: Each implementation requires dedicated infrastructure; no native multi-tenant SaaS model.

Documentation gaps: Some advanced features have limited documentation compared to commercial products.

Customisation complexity: Significant modifications require Grails/Groovy development expertise.

Deployment and operations

Self-hosted requirements:

Component	Minimum specification
Compute	2 CPU cores, 4 GB RAM (minimum), 4 cores/8 GB recommended
Database	MySQL 8.0+
Application server	Tomcat (bundled) or Docker
Java	OpenJDK 11+
Storage	50 GB+ depending on transaction volume

Deployment options:

Docker container deployment (recommended)
Traditional WAR deployment to Tomcat
DigitalOcean Marketplace one-click deployment
Azure deployment template

Operational overhead: Moderate. Standard Java application maintenance including updates, backups, and monitoring. Active community provides support through forums and documentation.

Integration capabilities

Integration type	Support level	Notes
REST API	●	Generic API for CRUD operations on all domain objects
Authentication	Session, API keys	Session cookies or API authentication
Bulk import	◐	CSV import for products, inventory, orders
Webhooks	○	Limited notification capabilities
Barcode scanning	●	Native support for 1D and 2D barcodes

Security assessment

OpenBoxes implements role-based access control with configurable permissions. User authentication supports local accounts and LDAP integration. Audit logging tracks data changes with user attribution.

TLS encryption protects data in transit. Database-level encryption provides data-at-rest protection when configured at the infrastructure layer.

The Eclipse Public License allows proprietary derivatives, providing flexibility for commercial implementations.

Cost analysis

Direct costs:

Cost category	Self-hosted estimate
Software licence	$0
Infrastructure (cloud)	$50-200/month for typical deployment
Implementation services	$10,000-50,000+ depending on scope
Training	Variable

Infrastructure costs by scale:

Scale	Monthly cloud cost estimate
Single warehouse, 5 users	$50-100
Multiple warehouses, 25 users	$100-200
Large deployment, 100+ users	$300-500+

Organisational fit

Best suited for:

Healthcare facilities managing pharmaceutical inventory
Humanitarian organisations managing emergency supplies
Organisations needing comprehensive lot and expiry tracking
Small-medium supply chain operations without ERP requirements

Less suitable for:

Manufacturing operations requiring production planning
Organisations needing integrated financial accounting
High-volume commercial distribution centres
Operations requiring advanced warehouse automation

ERPNext

Type: Open-source enterprise resource planning system Licence: GPL v3 Current version: 16 (December 2025) Deployment: Self-hosted, Docker, Frappe Cloud Source: https://github.com/frappe/erpnext Documentation: https://docs.erpnext.com

Overview

ERPNext is a comprehensive open-source ERP system covering accounting, sales, purchasing, inventory, manufacturing, HR, CRM, and projects. Developed by Frappe Technologies (India) and built on the Frappe Framework, ERPNext provides integrated business management where supply chain operations connect directly to financial accounting.

The Stock module provides inventory management with real-time valuation, warehouse management, and material tracking. Integration with Buying and Selling modules creates end-to-end procurement and sales order fulfilment workflows.

Capability assessment

ERPNext Stock module delivers comprehensive inventory management including multiple valuation methods (FIFO, weighted average, standard cost), warehouse hierarchies, bin locations, serial and batch tracking, and perpetual inventory with automatic accounting entries. Stock reservation against orders prevents overselling.

Procurement integrates purchase requisitions, RFQs, purchase orders, and goods receipt with supplier management and pricing. Manufacturing supports bills of materials, work orders, and production planning. Sales order fulfilment includes picking, packing, and delivery.

The integrated nature means stock transactions automatically create journal entries, eliminating reconciliation between inventory and financial systems. Multi-company and multi-currency support enables consolidated operations.

Key strengths

Full ERP integration: Stock management integrated with accounting, sales, purchasing, manufacturing, and other business functions in a single system.

Multiple valuation methods: FIFO, weighted average, and standard costing with automatic general ledger entries.

Active development: Regular releases with substantial community and commercial contributor base. Version 16 delivers significant performance and feature improvements.

Extensibility: Frappe Framework enables customisation through scripting, custom fields, and workflows without forking the codebase.

Key limitations

Complexity: Full ERP functionality creates a learning curve for teams only needing supply chain features.

Manufacturing focus: Warehouse management features target manufacturing and distribution rather than dedicated WMS scenarios.

Healthcare specifics: Lacks healthcare-specific features (pharmaceutical compliance, cold chain) present in purpose-built systems.

Performance at scale: Very large deployments (millions of transactions) may require optimisation and infrastructure investment.

Deployment and operations

Self-hosted requirements:

Component	Minimum specification
Compute	2 CPU cores, 4 GB RAM (minimum), 4+ cores/8+ GB recommended
Database	MariaDB 10.8+
Framework	Python 3.11+, Node.js 18+, Redis
Storage	20 GB+ depending on data volume

Deployment options:

Frappe Cloud (managed SaaS)
Docker deployment
Manual installation via Bench CLI

Operational overhead: Moderate. Frappe Bench CLI simplifies updates and site management. Self-hosted requires database administration and backup management.

Integration capabilities

Integration type	Support level	Notes
REST API	●	Full API access to all doctypes
Webhooks	●	Configurable on document events
Bulk import	●	Data Import Tool with validation
Authentication	API keys, OAuth, LDAP	Multiple methods supported
E-commerce	●	Webshop integration available

Security assessment

ERPNext implements role-based permissions at document, field, and action levels. Two-factor authentication supports TOTP. SSO integration available through Social Login Keys module.

Version 16 includes security enhancements with improved certificate validation. Frappe Cloud provides managed security including updates and monitoring.

Cost analysis

Direct costs:

Cost category	Estimate
Software licence	$0
Frappe Cloud hosting	$14-350+/site/month depending on tier
Self-hosted infrastructure	$50-500+/month depending on scale
Implementation services	$5,000-100,000+ depending on scope

Frappe Cloud pricing tiers:

Tier	Monthly cost	Included
Starter	$14	5 GB storage, community support
Professional	$49	20 GB storage, email support
Business	$179	50 GB storage, priority support
Enterprise	Custom	Custom requirements

Organisational fit

Best suited for:

Organisations needing integrated ERP with supply chain
Small-medium businesses seeking affordable full-featured ERP
Operations requiring manufacturing and inventory integration
Teams comfortable with open-source software management

Less suitable for:

Organisations only needing inventory management
Healthcare supply chains requiring pharmaceutical compliance features
Operations requiring dedicated WMS with advanced automation
Organisations needing enterprise vendor support agreements

Tryton

Type: Open-source business application platform Licence: GPL v3 Current version: 7.8 (December 2025) Deployment: Self-hosted, Docker, partner hosting Source: https://www.tryton.org Documentation: https://docs.tryton.org

Overview

Tryton is a modular business application platform providing ERP functionality through installable modules. Governed by the Tryton Foundation (Belgium), the platform emphasises code quality, test coverage, and clean architecture. The stock module provides inventory management, while additional modules add purchasing, sales, and other functions.

Tryton forked from TinyERP (later OpenERP/Odoo) in 2008, taking a different architectural direction emphasising stability and avoiding the commercial tensions that developed in the parent project.

Capability assessment

Tryton stock module tracks inventory across warehouses with support for lot tracking, multiple locations, and inventory valuation. Stock moves record all inventory changes with full audit trail. The module handles goods receipt, internal transfers, and goods issue with configurable workflows.

Perpetual inventory maintains real-time stock levels and valuation. Multiple valuation methods are supported. Integration with purchase and sale modules provides complete order-to-delivery workflows.

The modular architecture allows deploying only required functionality. This approach suits organisations wanting specific capabilities without full ERP complexity.

Key strengths

Code quality: Strong emphasis on testing, documentation, and clean architecture. The development approach prioritises reliability over feature proliferation.

European governance: Foundation governance based in Belgium without commercial control conflicts. GPL licence ensures software freedom.

Modular architecture: Install only required modules. Stock module operates independently or with purchasing/sales integration.

Historical data: Built-in data historisation tracks record states over time, enabling point-in-time reporting.

Key limitations

Smaller ecosystem: Fewer third-party integrations and implementation partners than larger ERP platforms.

Interface design: Functional but less polished user interface than commercial alternatives.

Limited cloud options: No central SaaS offering; cloud hosting requires partner arrangements.

Documentation accessibility: Technical documentation is thorough but may assume developer knowledge.

Deployment and operations

Self-hosted requirements:

Component	Minimum specification
Database	PostgreSQL 12+
Python	3.9+
Application	Tryton server and modules
Client	Web client (SAO) or desktop GTK client

Deployment options:

Docker container (official images)
pip installation from PyPI
Distribution packages (Debian, Fedora)

Operational overhead: Low-moderate. Well-tested upgrade paths between versions. Release cycle delivers new major version every 6 months with 1-year support (5 years for LTS releases).

Integration capabilities

Integration type	Support level	Notes
REST API	●	JSON-RPC and XML-RPC protocols
Webhooks	○	Limited native support
Bulk import	●	CSV import utilities
Authentication	Session-based, LDAP	LDAP via module

Security assessment

Tryton implements model-level access control with configurable permissions. The architecture separates client and server, with all business logic executing server-side.

TLS encryption protects client-server communication. Database security follows PostgreSQL best practices.

Cost analysis

Direct costs:

Cost category	Estimate
Software licence	$0
Self-hosted infrastructure	$30-200/month depending on scale
Implementation services	$10,000-50,000+ depending on scope
Partner support	Varies by partner

Organisational fit

Best suited for:

Organisations preferring European-governed open source
Operations wanting modular ERP deployment
Technical teams comfortable with self-hosting
Businesses requiring historical data tracking

Less suitable for:

Organisations needing turnkey cloud deployment
Teams requiring extensive third-party integrations
Operations needing dedicated WMS features
Organisations preferring commercial support agreements

Microsoft Dynamics 365 Supply Chain Management

Type: Cloud-based enterprise supply chain management Licence: Proprietary (subscription) Current version: 10.0.46 (December 2025) Deployment: Cloud SaaS only (Microsoft Azure) Documentation: https://learn.microsoft.com/en-us/dynamics365/supply-chain/

Overview

Dynamics 365 Supply Chain Management is Microsoft’s enterprise-grade supply chain platform within the Dynamics 365 suite. The platform covers warehouse management, inventory control, procurement, manufacturing, transportation, and demand planning as cloud-native services on Microsoft Azure.

The platform targets medium-to-large enterprises requiring sophisticated supply chain capabilities integrated with Microsoft’s broader business application ecosystem including Dynamics 365 Finance, Power Platform, and Microsoft 365.

Capability assessment

Supply Chain Management provides comprehensive warehouse management with advanced features including wave processing, work policies, location directives, and mobile warehouse app for floor operations. Inventory management supports multiple valuation methods, dimensions (site, warehouse, location, batch, serial), and reservation policies.

Procurement covers requisitions, RFQs, purchase agreements, vendor management, and collaboration portals. Manufacturing supports discrete, process, and lean manufacturing modes. Transportation management handles carrier selection, rate shopping, load planning, and freight reconciliation.

Copilot AI features assist with demand forecasting, supply planning, and operational insights. Integration with Power Platform enables workflow automation and custom applications.

Key strengths

Enterprise capabilities: Comprehensive supply chain functionality matching or exceeding capabilities of legacy on-premises ERP systems.

Microsoft ecosystem integration: Native integration with Microsoft 365, Power Platform, Azure, and other Dynamics 365 applications.

Continuous updates: Regular feature releases without disruptive upgrades. Version updates deploy automatically with optional preview testing.

Global scale: Multi-company, multi-currency, multi-language capabilities for global operations with regional compliance features.

Key limitations

Cloud-only deployment: No on-premises option. Organisations requiring data sovereignty outside Azure regions face constraints.

Cost structure: Per-user licensing creates high costs for organisations with many warehouse or operational users.

Complexity: Enterprise feature set requires significant implementation effort and ongoing administration.

CLOUD Act exposure: US-headquartered vendor means US government can compel data access regardless of data centre location.

Deployment and operations

Deployment model: Software-as-a-service on Microsoft Azure. No infrastructure management required.

Mobile warehouse app: Offline-capable mobile application for warehouse operations running on Android, iOS, and Windows devices.

Environments: Sandbox and production environments included. Additional environments available for purchase.

Update cycle: Continuous updates with 10 release waves per year. Preview environments allow testing before production deployment.

Integration capabilities

Integration type	Support level	Notes
REST/OData APIs	●	Comprehensive data entity exposure
Webhooks	●	Business events for external notification
Power Platform	●	Native integration with Power Automate, Power Apps
Azure services	●	Event Grid, Service Bus, Logic Apps
EDI	●	Built-in EDI translation and partner management

Security assessment

Dynamics 365 inherits Azure security including Azure Active Directory authentication, conditional access, and multi-factor authentication. Role-based security controls access to functions and data. Audit logging tracks data changes and user actions.

SOC 2 Type II and ISO 27001 certifications cover the service. Data encryption at rest and in transit is standard. Regional data centres support EU and other data residency requirements within Azure regions.

Cost analysis

Licence costs:

Licence type	Monthly cost per user
Supply Chain Management	$180
Activity (limited)	$30
Device (shared)	$75

Additional costs:

Additional environments: varies
Storage beyond included: $40/GB/month
Sandbox environments: included (limited)

Nonprofit pricing: Microsoft Nonprofit program offers up to 75% discount for qualifying organisations through Tech Soup or direct application.

Total cost example (50 users):

Component	Annual cost estimate
10 full users @ $180/month	$21,600
40 activity users @ $30/month	$14,400
Implementation (partner)	$150,000-500,000
Annual partner support	$50,000-150,000

Organisational fit

Best suited for:

Medium-large enterprises with complex supply chain requirements
Organisations heavily invested in Microsoft ecosystem
Global operations requiring multi-company, multi-currency support
Businesses needing advanced warehouse management features

Less suitable for:

Small organisations (cost prohibitive)
Organisations requiring on-premises or self-hosted deployment
Operations concerned about US jurisdiction over data
Simple inventory management without ERP requirements

SAP Business One

Type: Enterprise resource planning for small-medium business Licence: Proprietary (perpetual or subscription) Current version: 10.0 SP 2505 (2025) Deployment: On-premises (MS SQL or SAP HANA), SAP cloud Documentation: https://help.sap.com/docs/SAP_BUSINESS_ONE

Overview

SAP Business One is SAP’s ERP solution targeting small and medium-sized enterprises. The platform provides integrated business management including financials, sales, purchasing, inventory, manufacturing, and service. Unlike SAP S/4HANA which targets large enterprises, Business One suits organisations with simpler requirements and smaller IT teams.

The system originated as TopManage in Israel (1996), acquired by SAP in 2002. It operates on either Microsoft SQL Server or SAP HANA databases, with deployment options including on-premises and SAP-managed cloud.

Capability assessment

SAP Business One inventory management tracks stock across multiple warehouses with bin location support. The system handles serial and batch tracking, multiple valuation methods (moving average, FIFO, standard cost), and perpetual inventory with automatic accounting entries.

Purchasing covers purchase orders, goods receipt, vendor invoicing, and payment processing. MRP (Material Requirements Planning) generates procurement recommendations based on demand. Sales integrates quotations, orders, delivery, and invoicing.

Pick and pack functionality supports warehouse operations. Production management handles bills of materials and production orders for light manufacturing.

Key strengths

Integrated ERP: Complete business management with inventory, accounting, sales, purchasing, and basic manufacturing in one system.

On-premises option: Deploy on organisation-controlled infrastructure for data sovereignty requirements.

Established ecosystem: Large partner network with regional implementations and industry extensions.

SAP heritage: Benefits from SAP’s enterprise experience adapted for smaller organisations.

Key limitations

User licence costs: Per-user pricing creates costs that scale linearly with headcount.

Limited warehouse features: Warehouse management is basic compared to dedicated WMS. Advanced features require partner add-ons.

Implementation dependency: Most implementations require partner involvement for setup and customisation.

Upgrade complexity: Major version upgrades require planning and may impact customisations.

Deployment and operations

On-premises requirements:

Component	Specification
Database	Microsoft SQL Server 2019+ or SAP HANA
Operating system	Windows Server 2019+
Clients	Windows desktop (native), Web Client, mobile apps
Hardware	Varies by user count and database choice

Deployment options:

On-premises (MS SQL Server)
On-premises (SAP HANA)
SAP Business One Cloud (managed hosting)

Operational overhead: Moderate. Requires database administration, backup management, and version update planning. Partners handle most maintenance under support agreements.

Integration capabilities

Integration type	Support level	Notes
Service Layer API	●	RESTful API for data access
DI-API	●	COM-based data interface
Integration Framework (B1i)	●	XML-based workflow integration
SDK	●	UI and data extensibility

Security assessment

SAP Business One implements user-based licensing with role and permission controls. Data encryption at rest depends on database configuration. TLS protects data in transit.

SAP HANA deployment provides additional security features including dynamic data masking. Audit logging tracks transactions and changes.

Cost analysis

Licence costs:

Licence type	Approximate cost
Professional User	$2,500-3,000 perpetual + 20% annual maintenance
Limited User	$1,200-1,500 perpetual + maintenance
Indirect Access	Varies by usage

Subscription alternative: Monthly subscription pricing available, approximately $100-150/user/month.

Implementation costs: $25,000-150,000+ depending on scope, customisation, and data migration.

Partner discounts: Some SAP partners offer discounts for nonprofits, but no central programme exists.

Organisational fit

Best suited for:

Small-medium businesses needing integrated ERP
Organisations wanting on-premises deployment option
Operations with straightforward supply chain requirements
Businesses planning SAP ecosystem adoption

Less suitable for:

Large enterprises (limited scalability)
Complex warehouse operations requiring WMS
Organisations seeking low-cost open-source solutions
Healthcare supply chains needing specialised compliance features

Selection guidance

Decision framework

                              +------------------------+
                              | Supply chain platform  |
                              | selection              |
                              +-----------+------------+
                                          |
                      +-------------------+-------------------+
                      |                                       |
              +-------v-------+                       +-------v-------+
              | Health sector |                       | General       |
              | supply chain? |                       | business?     |
              +-------+-------+                       +-------+-------+
                      |                                       |
          +-----------+-----------+               +-----------+-----------+
          |                       |               |                       |
    +-----v-----+           +-----v-----+   +-----v-----+           +-----v-----+
    | Requisit. |           | Inventory |   | Need full |           | Inventory |
    | workflow  |           | focused   |   | ERP?      |           | only      |
    | focus     |           |           |   |           |           |           |
    +-----+-----+           +-----+-----+   +-----+-----+           +-----+-----+
          |                       |               |                       |
    +-----v-----+           +-----v-----+   +-----v-----+           +-----v-----+
    | OpenLMIS  |           | OpenBoxes |   | Yes       |           | OpenBoxes |
    |           |           |           |   |           |           | or ERPNext|
    +-----------+           +-----------+   +-----+-----+           +-----------+
                                                  |
                              +-------------------+-------------------+
                              |                                       |
                      +-------v-------+                       +-------v-------+
                      | Open source   |                       | Commercial    |
                      | preference    |                       | preference    |
                      +-------+-------+                       +-------+-------+
                              |                                       |
                  +-----------+-----------+               +-----------+-----------+
                  |                       |               |                       |
            +-----v-----+           +-----v-----+   +-----v-----+           +-----v-----+
            | ERPNext   |           | Tryton    |   | Microsoft |           | SAP       |
            | (general) |           | (modular) |   | ecosystem |           | Business  |
            +-----------+           +-----------+   | preferred |           | One       |
                                                    +-----+-----+           +-----------+
                                                          |
                                                    +-----v-----+
                                                    | Dynamics  |
                                                    | 365 SCM   |
                                                    +-----------+

Recommendations by context

Organisations with minimal IT capacity

For organisations with no dedicated IT staff managing supply chain alongside other duties:

Recommended: OpenBoxes (managed hosting) or ERPNext (Frappe Cloud)

OpenBoxes managed hosting removes infrastructure management burden while providing comprehensive inventory management. Partners In Health offers hosted services. The platform’s healthcare focus provides relevant features without unnecessary complexity.

ERPNext on Frappe Cloud provides broader ERP functionality with managed infrastructure. The $14/month starting tier suits small organisations testing the platform before scaling.

Avoid: Self-hosted deployments of any platform, Dynamics 365 (complexity and cost), SAP Business One (implementation complexity).

Pragmatic minimum approach:

Start with cloud-hosted solution
Focus on core inventory tracking and stock movements
Defer advanced features (demand planning, warehouse optimisation) until operational basics are stable
Plan for 1-2 weeks initial setup with vendor or partner support

Organisations with established IT functions

For organisations with dedicated IT teams (2-5 staff) able to manage infrastructure:

Recommended: ERPNext (self-hosted) or Tryton

ERPNext provides comprehensive ERP functionality including supply chain, accounting, and other business functions in an integrated platform. Self-hosting gives control over data and customisation. The active community and documentation support self-managed deployments.

Tryton suits organisations preferring European-governed software with modular deployment. Install only required modules, avoiding unused ERP complexity.

Consider: OpenLMIS for health supply chain operations with requisition-based ordering requirements. The microservices architecture requires container orchestration skills but provides purpose-built health logistics functionality.

Implementation approach:

Deploy in staging environment for testing and configuration
Plan data migration from existing systems
Train key users before go-live
Phase rollout by location or function to manage change
Allocate ongoing capacity for maintenance and updates

Organisations with specific constraints

Data sovereignty requirements:

For organisations requiring complete control over data location:

Self-hosted open source (OpenLMIS, OpenBoxes, ERPNext, Tryton) with infrastructure in required jurisdiction
SAP Business One on-premises with local hosting
Avoid cloud-only options without regional data centre commitments

High-volume commercial operations:

For distribution centres processing thousands of transactions daily:

Dynamics 365 Supply Chain Management provides enterprise warehouse management features
Consider dedicated WMS if supply chain is primary focus without broader ERP needs

Pharmaceutical and regulated supply chains:

For operations requiring GDP compliance, serialisation, or cold chain management:

OpenLMIS or OpenBoxes provide healthcare-specific features
Dynamics 365 with pharmaceutical industry extensions
SAP Business One with partner add-ons for pharmaceutical compliance

Migration paths

From	To	Complexity	Approach	Timeline estimate
Spreadsheets	OpenBoxes	Low	Direct data import via CSV	2-4 weeks
Spreadsheets	ERPNext	Low-Medium	Data Import Tool with validation	2-4 weeks
OpenBoxes	ERPNext	Medium	API-based extraction, transformation, load	2-3 months
OpenLMIS	OpenBoxes	Medium	Data export, mapping, parallel operation	3-6 months
Legacy ERP	Dynamics 365	High	Partner-led migration project	6-12 months
Legacy ERP	SAP Business One	High	Partner-led migration with data validation	4-9 months

Migration considerations:

Data quality: Clean source data before migration. Address duplicates, incomplete records, and inconsistencies.
Historical data: Determine requirements for transaction history. Most systems import opening balances rather than full history.
Parallel operation: Run old and new systems simultaneously during transition. Reconcile regularly to catch discrepancies.
User training: Plan training concurrent with technical migration. Users need proficiency before go-live.
Integration updates: Map integrations from old to new system. Test all integration points before cutover.

External resources

Official documentation

Open source platforms

Platform	Documentation	API reference	GitHub repository
OpenLMIS	https://docs.openlmis.org	Per-service RAML docs	https://github.com/OpenLMIS
OpenBoxes	https://docs.openboxes.com	https://docs.openboxes.com/en/develop/api-guide/	https://github.com/openboxes/openboxes
ERPNext	https://docs.erpnext.com	https://docs.erpnext.com/	https://github.com/frappe/erpnext
Tryton	https://docs.tryton.org	https://docs.tryton.org	https://hg.tryton.org

Commercial platforms

Platform	Documentation	API reference	Trust/security
Dynamics 365 SCM	https://learn.microsoft.com/en-us/dynamics365/supply-chain/	https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/	https://www.microsoft.com/en-us/trust-center
SAP Business One	https://help.sap.com/docs/SAP_BUSINESS_ONE	https://help.sap.com/docs/SAP_BUSINESS_ONE_SDK	https://www.sap.com/about/trust-center.html

Relevant standards

Standard	Description	URL
GS1	Global standards for supply chain identifiers and barcodes	https://www.gs1.org
GDP	Good Distribution Practice for pharmaceutical logistics	https://www.ema.europa.eu/en/human-regulatory-overview/post-authorisation/compliance-good-practices
IATI	International Aid Transparency Initiative for development data	https://iatistandard.org