Skip to main content

Entrupy App Workflows

For internal business operations, Entrupy provides the Entrupy app—a ready-to-use mobile application. Your teams can use it directly to perform authentications and fingerprinting, often with Entrupy-provided specialized hardware (e.g., microscopic lenses for luxury authentication and fingerprinting).

  • Authenticating Users: Your internal teams (e.g., warehouse staff, authenticators, operations personnel, customer support for item verification).
  • Capture Method: The Entrupy app guides your staff through the image capture process using the device camera or specialized Entrupy hardware, depending on the item type and task.

All data generated via the Entrupy app, including authentication results and fingerprinting records, can be accessed via the Entrupy API. This enables integration with your backend systems for reporting, inventory management, and other operational needs by using the customer_item_id provided during the app workflow. See API Integration for more details.

Core Authentication Workflow​

This workflow is for standard, individual item authentications performed by your business teams using the Entrupy app. It's suited for scenarios like one-off inventory checks, authenticating items at intake, or in-person appraisals.

General Process​

  1. Perform Authentication in Entrupy App:
    • An operator selects the item and initiates an authentication session in the Entrupy app.
    • They input the item's customer_item_id (e.g., by typing, scanning a barcode/QR code). This ID is important for tracking and later API lookups.
    • The app guides the operator through capturing images (with standard camera or specialized lens as required) and selecting item details (brand, material, etc.).
    • The operator submits the data through the app for Entrupy processing.
  2. Monitor Results:
    • Operators can see results directly in the Entrupy app upon completion.
    • Your backend systems can retrieve results and certificate information via the Entrupy API using the customer_item_id or by configuring webhooks for notifications.

Business Scenarios​

  • Authenticating On-Hand Inventory: Quickly verify items before purchase or listing (e.g., resellers, pawnshops).
  • Warehouse Intake/QC: Authenticate individual items upon arrival at warehouses or during quality control spot-checks.
  • In-Person Authentication: For trade-ins or verifying items from suppliers before purchase.

Workflows for Batch Operations​

These workflows are for authenticating a high volume of items using the Entrupy app, often integrated with your existing inventory management and processing pipelines. While the Entrupy app processes items one at a time through its interface, these patterns help manage such operations at scale.

Note: The authentication step can occur at any point in your process that makes sense for your operations. The scenarios below focus on the timing of Entrupy authentication relative to when your platform assigns or uses its customer_item_id.

Your platform is responsible for managing the "batch" or queue of items and corresponding customer_item_ids. Entrupy provides the App for capture by your operators, and the API for your backend to retrieve results.

Authentication after record creation is recommmended as it's simpler, but before and after are both possible.

Authentication After Record Creation​

Workflow: Your internal system (e.g., inventory management, WMS) already contains records for the items, each with a unique customer_item_id. Operators use the Entrupy app to authenticate these items.

Implementation:

  1. Item Record Exists: The item is registered in your system with a known customer_item_id.
  2. Operator Initiates App Capture: An operator identifies a physical item for authentication (e.g., from a work queue, by scanning a barcode on the item that reveals your customer_item_id).
  3. customer_item_id Entry: The operator enters this customer_item_id into the Entrupy app at the start of the session (typically in the SKU field).
  4. Image Capture & Submission: The operator completes image capture and data entry in the Entrupy app and submits.
  5. Result Retrieval (Backend): Your backend system monitors for results using the customer_item_id (via API polling or webhooks) and updates your internal item record.

Authentication Before Record Creation​

Workflow: An item is authenticated using the Entrupy app before it has a formal record or permanent customer_item_id in your primary backend system. This is less common for App-based flows but can occur if, for instance, items are authenticated at a preliminary receiving stage.

Implementation:

  1. Operator Initiates App Capture: An operator authenticates an item for which no customer_item_id from your main system yet exists or is readily available.
  2. Temporary Identifier (Optional but Recommended): If possible, the operator enters a temporary identifier (e.g., a sequential number, a lot number + item number) into the Entrupy app's customer_item_id (SKU) field. This temporary ID should be physically associated with the item (e.g., a sticker).
  3. Image Capture & Submission: The operator completes the authentication in the Entrupy app. The app will also have its own Entrupy-generated session ID.
  4. Record Entrupy ID / Temporary ID: Your operational process must ensure the Entrupy ID (visible in the app or retrievable via API if a temporary ID was used) or the temporary ID is recorded and stays with the physical item.
  5. Item Record Creation & customer_item_id Assignment: Later, your platform formally creates a record for the item and assigns its permanent customer_item_id.
  6. Link IDs for Result Retrieval:
    • If a temporary ID was used in the app: Your backend queries the API using this temporary ID to get results.
    • If only the Entrupy ID was noted: Your backend may need a process to map the Entrupy ID to your new customer_item_id for ongoing reference, or use the Entrupy ID directly for lookups if your system can store it.
    • (The v2 API endpoint to retrospectively add a customer_item_id to an existing Entrupy session is primarily designed for SDK workflows where the Entrupy ID is programmatically captured, but could theoretically be used if Entrupy IDs are meticulously tracked from app sessions).
  7. Platform Update: Your system updates the newly created item's record with the authentication outcome.

Considerations for App-based "Before Record Creation": This flow requires a robust manual process for tracking temporary IDs or Entrupy IDs and associating them with physical items until they are fully registered in your system. Using the customer_item_id (SKU) field in the app, even with a well-managed temporary ID, is generally the most straightforward way to ensure API retrievability.

Fingerprinting Workflows​

Entrupy's fingerprinting technology, accessed via the Entrupy app (often with the specialized microscopic lens), allows unique item identification. This is used for robust item comparison and to establish a secure chain of custody, particularly for returns management and internal tracking.

  • Primary Use Cases (App-based):
    • Returns Management: Register an item's fingerprint before it's shipped to a customer or leaves a secure area. When an item is returned, compare its fingerprint to the original registration to confirm it's the exact same item, helping to combat fraud.
    • Internal Tracking & Audits: Register fingerprints of high-value items in inventory and periodically perform comparisons to ensure items haven't been swapped or tampered with.

Fingerprint Registration​

This workflow describes how an item's unique fingerprint is initially captured and stored by your staff using the Entrupy app.

**Registration Methods (Entrupy App):

  1. Concurrent with Authentication: When an item is authenticated using the Entrupy app (for supported item types like luxury brands that require the lens), its fingerprint can often be automatically registered as part of that same app session.
  2. Dedicated Fingerprint Registration Flow: The Entrupy app (or the transitioning Entrupy FP app) provides a specific flow focused solely on fingerprint registration. This may be used for items not undergoing full authentication or to streamline the registration process.

General Process (Registration):

  1. Operator Initiates Registration: Using the Entrupy app (and lens), the operator starts a fingerprint registration session for an item.
  2. customer_item_id Entry: The operator enters the item's unique customer_item_id.
  3. Guided Capture: The app guides the operator through capturing the necessary microscopic images for fingerprinting.
  4. Submission & Storage: The data is submitted. Entrupy processes and stores the fingerprint, associated with the customer_item_id.
  5. API Access: Your backend can confirm registration status via API if needed.

Fingerprint Comparison​

This workflow describes how a previously registered fingerprint is compared against a new scan of an item by your staff using the Entrupy app, for example, when processing a return.

General Process (Comparison):

  1. Operator Initiates Comparison: For a returned item, the operator starts a fingerprint comparison session in the Entrupy app (using the lens).
  2. customer_item_id Entry: The operator enters the customer_item_id of the original item (the one that was initially registered and shipped).
  3. Guided Capture: The app guides the operator through capturing new microscopic images from the returned item.
  4. Submission & Comparison: The data is submitted. Entrupy compares the new scan against the registered fingerprint for the provided customer_item_id.
  5. Results in App & API:
    • The operator sees the comparison result (e.g., Match/No Match) directly in the Entrupy app.
    • Your backend can retrieve the detailed comparison result via the Entrupy API.

It is important that the customer_item_id is accurately entered during both registration and comparison to ensure the correct fingerprints are matched. Your operational procedures should ensure staff are trained on this. While the app provides immediate results, using the API allows for integration of these outcomes into your broader inventory or returns management systems.

Next Steps​