Samooha

Samooha calls Geoplan over REST and HTTPS for four warehouse RFID flows. Geoplan manages scan sessions, EPC data, and EPC-to-SKU mapping. Samooha remains the source of transaction documents and owns inventory updates.

The diagram shows the Samooha, warehouse, Geoplan middleware, and ON Principal connections:

Scope

Flow	Data exchange	Source document reference
Goods Receipt	Samooha sends the document, then retrieves scanned quantity per SKU	Purchase Invoice
Goods Delivery	Samooha sends the document	Sales Order
Customer Returns	Samooha sends the document	Credit Note
Vendor Returns	Samooha sends the document	Debit Note

Goods Delivery, Customer Returns, and Vendor Returns have no scan-result return leg. Every request still receives an HTTP acknowledgement.

RFID scope excludes put-away, picking, packing, stock transfer, and cycle count.

Integration rules

• Samooha initiates every integration exchange. Geoplan does not expose webhooks.
• Transaction calls use POST for audit integrity.
• Samooha filters transaction lines to RFID-enabled ON products.
• Product identity in transaction lines is the SKU. Barcode, VPM code, and product details come from synced master data.
• Geoplan returns SKU and scanned quantity for Goods Receipt. EPC values stay in Geoplan.
• One API key covers the Samooha integration within an environment.

Integration order

Page	Use
Authentication	Send the integration API key
Master Data	Load product data before transaction calls
Scan Activities	Use the four fixed activity IDs
Scan Sessions	Draft session API, flow rules, and known limitations
Errors & Retries	HTTP status reference