Product data / From intake to review

Less repeated work.
A clearer record of every decision.

Supplier files arrive with inconsistent names, incomplete identifiers and different structures. PackDossier brings lookup, validation and evidence into one repeatable workflow, so your team can focus on the exceptions.

Where it fits

Supplier onboarding

Normalize incoming records and check identifiers before preparing a new supplier catalogue for review.

Item-master maintenance

Repeat configured lookups as records change. Make gaps, conflicts and evidence visible instead of silently filling unknown values.

System migration preparation

Prepare native JSON or mapping previews against your current SAP MDG, Maximo, NetSuite or EDI definition.

Mapping previews require customer-specific templates and acceptance testing. They are not a claim of certified connectors or automatic production writeback.

Accuracy is a review process

Trace the value

See which configured source returned a value and when it was retrieved. A matching score does not replace source evidence.

Keep uncertainty visible

Unmatched identifiers, contradictory values and processing failures remain separate outcomes. The system does not turn an unresolved row into an approved record.

Approve the result

Your authorized reviewer decides what can be used. Acceptance criteria and the destination schema are agreed for each deployment.

The software is designed to reduce repetitive handling; accuracy and time savings must be measured on your representative data. It does not guarantee error-free output.

Customer-managed processing. Company-controlled access.

Your environment

Documents, results and provider keys

The customer-managed runtime reads and writes files in your environment. Your organization supplies and controls the credentials for its selected processing and catalogue providers.

  • Source records and outputs stay in your processing environment.
  • Selected third-party providers receive the information needed for the requests you configure.
  • Blue Ridge does not receive document contents through the licensing interface.

Blue Ridge account service

Identity, licensing and usage

Company membership, a company-bound API key, access status and usage allowances are managed through your Blue Ridge account.

  • Usage messages contain opaque job IDs, counts, status and runtime version.
  • Account, billing and network metadata are processed by the service.
  • Key revocation or suspension prevents new authorized processing.

This boundary applies to the customer-managed runtime, not the separate hosted PackDossier pilot. It is not a zero-knowledge certification. Work already sent to a provider may finish; access suspension does not delete customer-held files. Deployment and provider choices require a security review appropriate to the data.

A defined commercial agreement

  1. 01Scope a pilot

    Agree representative inputs, required fields and an acceptance test.

  2. 02Approve the order

    Specify the monthly minimum, included rows, overage rate and spending cap.

  3. 03Activate your company

    Sign in, receive approved access and issue a company-bound key.

  4. 04Review usage

    See processed-row counts and a usage statement for the agreed billing period.

Enterprise orders are invoiced under agreed terms. Provider API costs are paid through the customer’s own provider accounts; Blue Ridge charges for its software and contracted support. Account registration alone creates no paid subscription.

Company keys are restricted to the issuing account and may be revoked. Suspension, renewal, refunds, support and continued access to customer-held outputs are defined in the order. Metering counts attempted rows under the agreed policy, including failed attempts; credits are shown separately.

Recorded evaluation, with the denominator

The repository includes an August 24, 2026 evaluation of 56 sampled rows across seven public bills of materials. It is a small historical sample, not an acceptance test for your deployment.

Recorded outcomes — 56 rows total
OutcomeRowsMeaning
Resolved13An external source returned a match; fields may still need review.
Held for review2Conflicting or ambiguous results.
Not queryable8No identifier accepted by a configured provider.
Unresolved2No confirmed match returned.
Parse blocked24Input could not pass the parsing stage.
Resolution failed7A lookup operation failed.

13/56 rows resolved (23.2%). Resolution rate is not an accuracy score. No percentage time-saving, production throughput or customer revenue claim is inferred from this test. A paid pilot should measure correctness, review time and total cost against your current process.

For government and prime-contractor teams

We scope the deployment against the solicitation, data classification, approved environment and required controls. The demonstration uses synthetic records. Do not submit CUI, classified material, export-controlled technical data or other restricted information through this public site.

SAM registration and a CAGE code identify the company. They do not establish FedRAMP authorization, CMMC certification, an agency ATO or approval to process a particular dataset. Those requirements must be evaluated for the proposed environment and contract.