- 01Accepted inputs identified by checksum
- 02Row, field and record-key counts reconciled where applicable
- 03Findings, rules and approvals kept in separate records
- 04Rejected, quarantined and unresolved items remain visible
- 05Every promised artifact listed in a SHA-256 manifest
Fixed-fee services for product and catalogue data
Understand your product data before you change it.
Start with a source-quality assessment, or choose a review of an existing result, a mapping blueprint or a transformation based on approved rules. Each service is defined by its inputs, deliverables and written scope.
Find a serviceData Integrity Assessment€3,900 / US$4,500 net · one-time
- Written scope
- Published service limits
- Specified deliverables
- No mandatory follow-on
Choose by the result you need
One decision. Five distinct scopes.
Choose the result you need. The Evidence Review checks an existing output and is a separate starting point. Other services do not require a preceding purchase if their own prerequisites are already met.
This checks only the published record cap. File size, fields, operations, formats and written scope still need to fit.
| Service / outcome | Published limits | One-time price, net | Record-cap check | Next step |
|---|---|---|---|---|
| Data Integrity AssessmentDIA-3900 Understand the quality of your source data and prioritise the issues to address. | 250,000 source records 150 source fields 50 MiB One CSV / flat JSON / passive XLSX file | €3,900 / US$4,500 | Enter a volume to check | Review scope |
| Independent Release Evidence ReviewEVD-7900 Review an existing result against its source and declared rules, with documented comparisons and deviations to support your own release decision. | 100,000 source records 150 source fields 100 target fields 100 approved operations 50 MiB Upload one source file, one existing result file and a versioned JSON rule file declaring the record key and comparisons. | €7,900 / US$9,500 | Enter a volume to check | Review scope |
| Release Readiness BlueprintMAP-12500 Document proposed mappings, required-field gaps and unresolved decisions in a blueprint for customer review. Mapping approval remains with you. | 100,000 source records 150 source fields 100 target fields 25 proposed transformations 50 MiB Upload one source file and one target schema as JSON. | €12,500 / US$14,500 | Enter a volume to check | Review scope |
| Verified Static File Transformation — CompactTRN-C-18900 Produce one flat CSV using approved operations, with validation results and a quarantine register for a source of up to 50,000 records. | 50,000 source records 150 source fields 50 target fields 10 approved operations 50 MiB Upload one source file, one target schema as JSON and the mapping you have approved as JSON. | €18,900 / US$22,000 | Enter a volume to check | Review scope |
| Verified Static File Transformation — StandardTRN-28000 Produce one flat CSV using approved operations, with validation results and a quarantine register for a source of up to 250,000 records. | 250,000 source records 150 source fields 100 target fields 25 approved operations 50 MiB Upload one source file, one target schema as JSON and the mapping you have approved as JSON. | €28,000 / US$32,000 | Enter a volume to check | Review scope |
Review the scope of each service. Your account keeps orders, payments and reports together.
Inspect the evidence before discussing an engagement
See what a handover contains. Start with a worked sample.
ORVELYNT keeps observed facts, declared rules, customer approvals and exceptions distinct. The linked sample uses invented data; it is an illustrative excerpt, not a customer reference or a complete commissioned delivery.
Acceptance checks must be agreed in writing.
Proposed checks cover file presence, readability, reconciled counts, agreed scope, approved mappings and declared validation rules. Economic outcomes, conversion, publication and legal compliance are outside technical acceptance.
Review against the checksum manifest
File handling and scope
Files are processed within the agreed scope and without access to live systems. Unsupported or potentially sensitive inputs are rejected. Before files are provided, the written scope must specify which deliverables may contain source values and how those files will be handled. Required mappings need customer approval; quarantined records remain outside the main output.
Files are uploaded privately through your account
Start with your data and intended result
Find a service.
Choose your available input, intended result and main data problem. For a transformation, also choose a size tier. Review the suggested service and its limits, then copy or download your project summary. Final scope acceptance requires a separate review.
The page link reflects your current choices. ‘Restore the DIA example’ replaces them with a CSV source, a source profile and a source-quality assessment.
Choose the service that matches your next decision
Five services. No recurring contract.
Each service has its own scope and deliverables. Choose your service, create an account and upload your files. No enquiry or sales call is required.
No subscription.No automatic renewal.No mandatory follow-on.
01
DIA-3900 · For an unclear source
Data Integrity Assessment
€3,900 / US$4,500net · one-time
- Scope
- One CSV, flat JSON or single-sheet passive XLSX file; up to 50 MiB, 250,000 records and 150 fields.
- What you receive
- Executive report in PDF
- analysis workbook
- machine-readable profile
- field-level report on completeness, types and uniqueness
- prioritised issue register
- methodology
- SHA-256 manifest.
- Required inputs
- Upload one source file and confirm your right to have it processed.
- Target delivery
- Delivered within three business days from confirmed payment receipt. Your files are checked before payment.
- Boundary
- No data correction, target comparison, mapping, certification, marketplace acceptance, API or system access.
02
EVD-7900
Independent Release Evidence Review
€7,900 / US$9,500net · one-time
- Scope
- One source and one existing result file: CSV, flat JSON or single-sheet passive XLSX, each up to 50 MiB and 100,000 records. Up to 150 source fields, 100 result fields, 100 comparisons and 100 declared operations. JSON rules up to 2 MiB. The automatic review accepts up to 200,000 recorded deviations.
- What you receive
- Count reconciliation and a register of missing, additional and duplicate records
- comparisons against the declared rules and a CSV of deviations
- executive evidence report and workbook
- snapshot of the reviewed rules and a checksum manifest.
- Required inputs
- Upload one source file, one existing result file and a versioned JSON rule file declaring the record key and comparisons.
- Target delivery
- Delivered within five business days from confirmed payment receipt. All three files are checked before payment.
- Boundary
- Deterministic evidence only; not certification, release approval or a guarantee of downstream acceptance.
03
MAP-12500
Release Readiness Blueprint
€12,500 / US$14,500net · one-time
- Scope
- One source and one customer-supplied target schema; up to 50 MiB, 100,000 source records, 150 source fields, 100 target fields and 25 proposed transformations. Source: CSV, flat JSON or single-sheet passive XLSX. Target schema: JSON, up to 2 MiB.
- What you receive
- Source-to-target mapping matrix with confidence assessments and reasoning for the proposed mappings
- analysis of gaps in required target fields
- JSON/YAML blueprint
- one consolidated written revision.
- Required inputs
- Upload one source file and one target schema as JSON.
- Target delivery
- Work starts within five business days from receipt of the 70% order payment. The blueprint is delivered within seven business days from that payment; one consolidated written revision is included.
- Boundary
- Mappings remain suggested, unmapped or blocked until customer approval; no transformed production output is implied.
04
TRN-C-18900
Verified Static File Transformation — Compact
€18,900 / US$22,000net · one-time
- Scope
- One source file, up to 50 MiB; CSV, flat JSON or single-sheet passive XLSX. Up to 50,000 source records, 150 source fields, 50 target fields, 10 approved operations and one flat CSV output. Target schema and approved mapping: JSON, up to 2 MiB each.
- What you receive
- Flat CSV result checked against the agreed validation rules
- quarantine register
- validation summary
- SHA-256 manifest
- deterministic configuration
- runbook.
- Required inputs
- Upload one source file, one target schema as JSON and the mapping you have approved as JSON.
- Target delivery
- Work starts within five business days from receipt of the 70% order payment. Delivery within ten business days from that payment. Approved mappings are checked before payment.
- Boundary
- No APIs, production writes, schedules, hosting, monitoring, recurring support or third-party acceptance guarantee.
05
TRN-28000
Verified Static File Transformation — Standard
€28,000 / US$32,000net · one-time
- Scope
- One source file, up to 50 MiB; CSV, flat JSON or single-sheet passive XLSX. Up to 250,000 source records, 150 source fields, 100 target fields, 25 approved operations and one flat CSV output. Target schema and approved mapping: JSON, up to 2 MiB each.
- What you receive
- Flat CSV result checked against the agreed validation rules
- quarantine register
- validation summary
- SHA-256 manifest
- deterministic configuration
- runbook.
- Required inputs
- Upload one source file, one target schema as JSON and the mapping you have approved as JSON.
- Target delivery
- Work starts within five business days from receipt of the 70% order payment. Delivery within fifteen business days from that payment. Approved mappings are checked before payment.
- Boundary
- No APIs, production writes, schedules, hosting, monitoring, recurring support or third-party acceptance guarantee.
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.
05 / Data Integrity Assessment
A clear starting point
Understand the quality of one source file.
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.
Net fee · one-time€3,900 / US$4,500
One flat product or catalogue file
CSV, flat JSON or passive XLSX; up to 50 MiB, 250,000 records and 150 fields. Processing rights must be confirmed and personal, payment, health or credential data must not be included.
- Executive PDF and analysis workbook
- Machine-readable source profile
- Field-level completeness, type and uniqueness report
- Prioritised issue register, methodology and SHA-256 manifest
100% at booking
Your report is delivered within three business days from confirmed payment receipt. Your files are checked before you pay.
Assessment is not transformation
No data correction, target comparison, mapping, certification, marketplace acceptance, API connection, system access or production write is included.
Source → rules → exceptions → evidence
A documented process, from input to handover.
Each service records the inputs, checks and deliverables relevant to its written scope. Transformations use customer-approved operations within the selected service limits.
S→
Accepted source
Validate the declared flat-file input and record its checksum, structure and agreed scope before processing.
Source registerR→
Explicit rules
Document declared comparisons, suggested mappings or customer-approved operations only where the selected offer permits them.
Rule registerT→
Controlled transformation
For Compact or Standard only, apply the approved operations to the bounded offline file flow.
Transformation recordX→
Legible exceptions
Reject unsupported inputs and keep quarantined or unresolved records outside the main output.
Exception registerE
Evidence package
Deliver the commissioned artifacts with objective acceptance evidence and a SHA-256 manifest.
Handover with a checksum manifestAccepted source0.4 kgERP / net weight
×1000Transformation400Weight converted from kilograms to grams
→Target sample400 gResult shown in grams
Common product-data problems
See where your product data needs attention.
Missing values, duplicate identifiers and unclear mappings make product data harder to use. ORVELYNT documents findings within the agreed scope so your team can decide what to address next.
Supplier structures
Names, units, identifiers and columns arrive without one agreed interpretation.
Incomplete fields
Required product attributes remain empty, conflicting or impossible to classify safely.
Duplicate identifiers
Repeated or colliding record keys make counts and downstream reconciliation unreliable.
Type and unit conflict
Values appear valid while their type, scale or unit changes the commercial meaning.
Release deviation
An already generated result differs from its source or declared rules without visible evidence.
Discuss your product-data requirements.
Choose a service, or describe your requirements for an enterprise engagement, paid pilot, implementation or larger contract.
Paid pilot
Propose one bounded scenario, agreed inputs and a measurable acceptance check. Define the evidence needed for a stop, adapt or continue decision before wider work.
Implementation
Scope the approved solution, responsibilities, environments and handover. Integrations and production changes require a separate written engagement.
Enterprise engagement
Agree multiple workstreams, governance and procurement requirements. Deliverables, fees, responsibilities and support are defined in an individual proposal.
These are proposed engagement paths, subject to delivery confirmation and a written paid scope. Any later phase requires a separate decision and written scope.