Tag: connectors
How a connector works
The mechanics of a connector: the outbound half that polls, maps and publishes, the inbound bridge that answers identity questions, and the design rules the code holds you to.
#connectors#sync#mapping#bridge#webhook#idempotencyIdentifiers: GTIN, SKU and What Identifies What
One product needs exactly one GS1 identifier: the GTIN. Where the connector finds it, why your SKU is a different thing, and how batch, serial and logistics-unit levels build on top.
#connectors#gtin#sku#lgtin#sgtin#sscc#check-digitEvents, Credentials and Representations
What happens after a record is published: how a movement in your source system becomes an EPCIS event, where UNTP answers the same question differently, and how a passport gains a signed, selectively disclosed representation.
#connectors#epcis#events#event-types#transformation#error-declaration#verifiable-credentials#untp#access-tiers#representationsThe UnoPim connector
The whole UnoPim route: what has to exist in the PIM, how the connection is configured, what the first sync publishes, and where the data surfaces in DDM and on the published passport page.
#connectors#unopim#pim#gtin#mapping#webhook#passportThe Odoo connector, step by step
One warehouse day walked through end to end: goods in, packed onto a pallet, shipped, part of it back, the rest ground into another article, and one report taken back, with the screen and the EPCIS event it produces side by side.
#connectors#odoo#epcis#events#sscc#aggregation#transformation#tutorialopenepcis_connector: products and contacts as GS1 master data
The base addon. Products and company contacts are queued on save and published to the catalog behind the GS1 Digital Link resolver; a GTIN can be drawn from your own prefix; the field mapping is data an administrator edits; the form says what a registry still wants before you publish.
#connectors#odoo#master-data#gtin#gln#field-mapping#offline-token#digital-linkopenepcis_connector_stock: lots and serial numbers
The bridge to Inventory. A lot becomes /01/<gtin>/10/<lot>, a serial number /01/<gtin>/21/<serial>, each a document of its own in the catalog under the product's GTIN: with the instance-level Digital Link and its QR code on the lot form, where labels are actually printed.
#connectors#odoo#lot#serial#lgtin#sgtin#instance#digital-linkopenepcis_connector_product_expiry: expiry dates as GS1 terms
A data-only bridge. Three mapping rows carry the dates Odoo's Expiration Dates app keeps on a lot: expiration date, best-before date, and an inactive sell-by row, into the per-instance catalog document under their GS1 names.
#connectors#odoo#expiry#best-before#lot#mappingopenepcis_connector_events: visibility events
Every validated transfer becomes an EPCIS 2.0 ObjectEvent, packing an AggregationEvent under an SSCC, a return a TransactionEvent, and a wrong report an error declaration. Three settings decide what is reported: the company switch, the operation type, the location, and an outbox keeps the warehouse from ever waiting on the repository. Partners' events come back into an inbox that shows and, where two settings agree, posts.
#connectors#odoo#epcis#events#objectevent#aggregationevent#sscc#gln#outbox#inbox#error-declarationopenepcis_connector_events_mrp: manufacturing events
The bridge to Manufacturing. A finished manufacturing order is reported as the one TransformationEvent it is: components in, goods out, and the claim that the second came from the first, which is the only thing in EPCIS that carries a chain of custody across a production step.
#connectors#odoo#mrp#transformationevent#epcis#chain-of-custodyopenepcis_connector_events_pos: point-of-sale events
The bridge to Point of Sale. A till's orders leave the warehouse through an operation type that looks exactly like a delivery to the stock module; this addon knows the difference and reports a sale as retail_selling with the goods retail_sold: and keeps that reading current as tills are configured and moved.
#connectors#odoo#pos#retail_selling#retail_sold#epcis#tillThe Odoo connector
Seven LGPL-3 addons that publish Odoo's products, contacts, lots and serial numbers to a GS1 Digital Link and report what happens to them as EPCIS 2.0 events: one page per addon, and a warehouse day walked through screen by screen.
#connectors#odoo#erp#addons#epcis#digital-link#lgplThe ERPNext connector
How the connector reads ERPNext over the Frappe REST API: the role, custom fields and webhooks the setup script creates, the connection settings, what is published for items, batches, serial numbers and parties, the default mapping, EPCIS events from stock documents, and the write-back into ERPNext.
#connectors#erpnext#frappe#erp#gtin#gln#webhook#epcisThe metasfresh connector
How the connector reads metasfresh over its REST API v2: the API token and its role, where GTIN and GLN come from, the connection settings, what is published for products and business partners, the default mapping, polling without webhooks, and the optional back-link through External References.
#connectors#metasfresh#erp#gtin#gln#polling#external-referencesThe Narravero connector
How the Narravero DPP Publisher and the OpenEPCIS catalog work together, what to set up on the Narravero side, where the GTIN comes from, how each passport gets a GS1 Digital Link on the brand's own domain, and what the connector writes back.
#connectors#narravero#dpp#tridy#gtin#resolver#digital-link#gs1:pipThe AAS connector: BaSyx and EDC
How the AAS connector reads Asset Administration Shells from Eclipse BaSyx, directly or through an Eclipse Dataspace Connector, and publish them to the OpenEPCIS catalog under a GS1 Digital Link with an EN 18223 passport behind it.
#connectors#aas#basyx#edc#dataspace#catena-x#digital-twin#dpp#digital-linkConnectors
Publish products from UnoPim, ERPNext, metasfresh, Odoo, Narravero or an Asset Administration Shell to a GS1 Digital Link, a digital product passport and EPCIS events.
#connectors#unopim#odoo#erpnext#metasfresh#narravero#aas#basyx#edc#digital-product-passport#epcis#resolver