Supplier structures
Names, units, identifiers and columns arrive without one agreed interpretation.
Private local preview · no data transfer
Controlled product-data evidence / worldwide
ORVELYNT accepts one bounded product-data problem and returns evidence, a customer-reviewable blueprint or a tested offline file result—without replacing the systems already in place.
The operational cost is carried between systems
A source file, target schema, declared rule set and generated result can each look plausible in isolation. The expensive uncertainty is the unrecorded difference between them: what changed, what was held, which decision was approved and what evidence remains.
Names, units, identifiers and columns arrive without one agreed interpretation.
Required product attributes remain empty, conflicting or impossible to classify safely.
Repeated or colliding record keys make counts and downstream reconciliation unreliable.
Values appear valid while their type, scale or unit changes the commercial meaning.
An already generated result differs from its source or declared rules without visible evidence.
Source → rules → exceptions → evidence
ORVELYNT keeps assessment, independent review, mapping design and approved static-file transformation as distinct scopes. No offer quietly becomes a live connector, system write or recurring service.
Validate the declared flat-file input and record its checksum, structure and agreed scope before processing.
Source registerDocument declared comparisons, suggested mappings or customer-approved operations only where the selected offer permits them.
Rule registerFor Compact or Standard only, apply the approved operations to the bounded offline file flow.
Transformation recordReject unsupported inputs and keep quarantined or unresolved records outside the main output.
Exception registerDeliver the commissioned artifacts with objective acceptance evidence and a SHA-256 manifest.
Manifest-bound handoverDefine the passage before defining the work
This private-preview instrument creates a local scope note in your browser. It has no upload field, sends nothing, stores nothing and is not a quotation, acceptance or feasibility promise.
The canonical first commission
ORVELYNT profiles one accepted product or catalogue file and returns a documented view of completeness, structure, duplicates, type inconsistencies and prioritised release risks. It does not correct the file or compare it with a target.
CSV, flat JSON or passive XLSX; up to 50 MB, 250,000 records and 150 fields. Processing rights must be confirmed and personal, payment, health or credential data must not be included.
Target delivery is five business days after a complete, scope-compliant file is accepted. A rejected or unsupported input does not proceed silently.
No data correction, target comparison, mapping, certification, marketplace acceptance, API connection, system access or production write is included.
Enter narrowly. Leave with command.
These names and prices follow the current canonical catalogue. Every commission stands alone; scope, file limits, prerequisites, delivered artifacts and acceptance criteria are visible before order.
Prices are net, one-time catalogue prices. Taxes and invoicing treatment depend on the contracting entity and buyer jurisdiction. Additional sources, targets, remediation or support require separate written scope.
Proof is an artifact, not a claim
ORVELYNT keeps observed facts, declared rules, customer approvals and exceptions distinct. No customer result, certification, marketplace acceptance, benchmark or economic outcome is implied by this private preview.
The customer checks file presence, readability, reconciled counts, agreed scope, approved mappings and declared validation rules. Economic outcomes, conversion, publication and legal compliance are outside technical acceptance.
The local product engine is documented as making no network calls or live-system writes, rejecting unsupported and likely sensitive inputs, excluding raw row values from reports, blocking unapproved required mappings and keeping quarantined rows out of the main output. Production customer upload remains separately gated and is not represented here as active.
Private local preview · no submission
The canonical entry is the Data Integrity Assessment. This preview stops at a local scope note: it does not upload a file, submit an order, contact anyone or create a recurring commitment.
Return to the private Assay€3,900 / US$4,500 net · one-time