Operating identity
The current footer identifies Accumark Labs as a DBA of Valence Analytical LLC at 1045 N Armando St, Suite D, Anaheim, California. The management page repeats one person and placeholder text across multiple roles.
← All testing lab reviewsOpen the COA checker
Testing laboratory · Reviewed 2026-09-03
Accumark Labs review
Valence Analytical LLC dba Accumark Labs · United States
- Operational read
- Operating DBA; accreditation pending
- Operating history
- Founding date not confirmed
- Accreditation
- ISO 17025 pending
Legitimacy review
Is Accumark Labs legit?
Accumark has a real disclosed DBA and an active testing offer, but it should not yet be called accredited. Capability timelines and early report methods need explanation, particularly where reports appear to predate advertised instrument availability.
Operating history and strongest evidence
Legal DBA disclosure, physical address, public service prices, turnaround policy, and a live verification contract.
Accreditation scope
The company says ISO 17025 is pending. No active accreditor certificate and scope was found.
Methods and intake
Accumark publishes HPLC identity, purity, and quantity, endotoxin, PCR sterility, and a full-panel price with typical 48-to-72-hour turnaround. LC-MS, NMR, residual solvents, and moisture are marked coming soon.
Public service record
A PeptideCritic article raised missing-identity questions that the newer DBA footer partially resolves. Other page-control and method-timeline issues still need primary explanation.
Important limits
Accreditation is pending; leadership copy, future-service dates, and earlier mass-spectrometry report attribution are inconsistent. An older criticism should carry an update where the company has since supplied the missing DBA disclosure.
COA verification
Can I check a Accumark Labs COA?
Enter the printed verification code or follow the certificate QR to the live Accumark record.
- Official destination
- Exact record permalink or public portal search
- What you need
- Verification code
- Exact-link rule
- Use /verify/{URL-encoded verification code} only when the code is printed or obtained from the issuer. The generic /verify form is the safe fallback.
- Stored identifiers complete?
- No
- Record-specific links?
- No
- Identifier copyable?
- No
Identifiers on the certificate
- Verification codeVerification or QR section of an Accumark-issued COA.
Result handling
How each verification state is reported
Exact match
Verify only when the live Accumark record reached by the printed code matches the retained certificate identity.
No match
An explicit official no-record response is unresolved evidence, not proof that the certificate is invalid.
Conflict
Quarantine the record when the identifier resolves to materially different issuer metadata; do not promote it.
Portal unavailable
Treat a CAPTCHA, login, timeout, outage, private record, or other portal failure as unknown.
Unsupported lab
Retain the certificate as document-only evidence and use the issuer contact route without claiming verification.
Unresolved
Keep the record unresolved until an exact issuer result or documented issuer confirmation is available.
Certificate structure
Multi-page and multi-panel reports
Multi-page
Both retained certificates are single-page; preserve future appendices and live-record revisions.
Multi-panel
Both records contain multiple reported scopes and should retain each result separately.
Evidence boundaries
What the record does—and does not—connect
- Certificate identity
- The retained file, fingerprint, and printed fields identify the certificate artifact.
- Issuer verification
- An exact issuer lookup confirms an issuer record for that certificate; it does not expand the reported scope.
- Tested sample
- The findings apply only to the sample described on the certificate.
- Product matching
- The seller product, strength, and lot must be matched to the tested sample separately.
- Physical-vial custody
- Neither the certificate nor its portal proves custody of the physical vial a buyer receives.
Review receipts
Records and discrepancies checked
Representative records
- coa:8e845503f55756917d60dd40Ascend Amino GHK-Cu lot GC003; retained without an Accumark verification code or exact record URL.
- coa:e7ad7c67517647fe279c753eSecond retained Accumark record; document-only despite the now-public issuer verification route.
Concrete discrepancies
- The provider registry still marks Accumark unsupported even though the official site now exposes a verification-code form and documents permanent record URLs.
- Neither retained certificate stores the verification code required by the official portal.
- No current displayed link reaches an Accumark record-specific destination.
Public search record
What current search results cover
The official site explains the verification model in detail. A third-party critique raises transparency questions; those opinions remain separate from record verification.
Sources
Evidence used for this review
- Accumark Labsofficial
- Accumark Labs verificationofficial_portal
- Accumark servicesofficial_method
Reusable integration rule: Promote only after extracting the printed code, validating the exact live record, and storing the record permalink independently from the PDF.
Check the document