Why this page exists
Our public-facing policies are only meaningful if the operational controls behind them are real. This page summarizes the internal controls Harker International maintains so that the claims made on SriLankaExport.com (verification, certificate review, sanctions screening, buyer acknowledgment, data protection) are defensible to buyers, vendors, partners, banks, payment processors, and regulators. It does not disclose the security-sensitive details of any control, but it states what each control exists for, what evidence is retained, and who is responsible.
1. Vendor onboarding file
What. A secure file for each vendor containing: business registration document, owner / contact details, tax / customs references, EDB registration / directory listing details where applicable (vendor-reported), product category declarations, vendor-submitted certificate copies, and the signed compliance declaration under the Vendor Agreement §4a.
Evidence retained. PDF / image copies, upload date, expiry date (where applicable), reviewer name, review status (Pending Review / Business Reviewed / Certificate Copy Reviewed / Certificate Expired / Suspended / Rejected).
Owner. Marketplace Operations.
2. Verification status labels
What. Consistent status taxonomy across vendor onboarding and per-certificate review, see the Richtlinie zur Verifizierung auf dem Marktplatz und Richtlinie zu Produktangaben bei Zertifikaten „&“. Status changes are recorded with reason and reviewer.
Evidence retained. Admin log of status changes with timestamp, reviewer, prior status, new status, reason.
3. Certificate expiry tracking
What. Every vendor-submitted certificate is tracked by name, status (Vendor-submitted / Copy reviewed / Pending update / On request / Verify per shipment), scope (company / facility / product / batch / shipment), issue date, expiry date, issuing body, and notes. Per-certificate status pills render next to each cert on the vendor profile, replacing the older flat list. Automated reminders are sent: a daily admin digest covers any certificate that has lapsed or that expires within the next 30 days; lapsed certificates may result in suspension of affected listings after notice to the vendor.
Evidence retained. Certificate register stored as JSON in the vendor’s WordPress user-meta (key _sle_vendor_certs_v2), plus the underlying documents in the vendor onboarding file (see §1).
Live status (2026-05-30). Data model, per-cert status pill rendering on the vendor profile + on single product pages, expiry-warning visual tone (warning color fires automatically when a cert is within 30 days of expiry), and the daily expiry digest cron are live. The digest is implemented as a WP-Cron event which is request-driven (fires on the next visit after the daily interval elapses), not a true real-time system cron, on low-traffic days the digest may be delayed by hours. End-to-end deliverability of the digest path to admin_email has been verified. Vendor self-service editing UI inside the WCFM dashboard is the next milestone, until it ships, the marketplace team edits cert metadata directly.
4. Official-mark control
What. Vendors may not display EDB, government, ministry, Sri Lanka Tea Board, SLSI, ISO, Fairtrade, Halal, Organic, GI, or other regulated marks unless authorized and accurate for the relevant product / facility scope. The Richtlinie zu Produktangaben bei Zertifikaten „&“ defines the standard. Unauthorized marks may be removed under the IP Infringement & DMCA Policy.
Evidence retained. Permission / authorization documents from the issuing body, and product-specific evidence (e.g. organic transaction certificate per shipment).
5. Product category compliance
What. Each product category onboarded to the platform has a category-specific compliance checklist covering documentation, certifications, and destination-country implications. The categories currently supported are listed in Kategorie-Exportanforderungen.
Evidence retained. Category compliance checklist completed at vendor onboarding per product / category.
6. Buyer acknowledgment
What. Before sending an RFQ or placing an order, the buyer accepts an electronic statement to the effect that SriLankaExport.com is an independent marketplace and that import eligibility, customs, duties, taxes, labeling, and document acceptance are the buyer’s responsibility. The acceptance is captured under the Sri Lanka Electronic Transactions Act.
Evidence retained. Timestamp, IP address, buyer account, terms version (current: ack-v1-2026-05-30), checkbox text version.
7. Payment risk review
What. High-value, unusual, restricted-product, high-risk-category, or mismatched buyer / vendor transactions are reviewed before payment release. See the AML & KYC Statement.
Evidence retained. Transaction risk notes, KYC documents, bank / payment records, decision log.
8. Data protection controls
What. Admin access to KYC and certificate documents is restricted; admin accounts require strong passwords and two-factor authentication; retention periods are defined; deletion process exists for data-subject requests; cross-border transfers are disclosed. See the Datenschutzerklärung und Data Processing Addendum.
Evidence retained. Access logs (where lawful), retention schedule, breach register.
9. Complaint and dispute process
What. Process for buyer disputes, fake certificates, wrong goods, non-delivery, chargeback, or regulatory complaint, see the Dispute Resolution & Buyer Protection policy.
Evidence retained. Ticket ID, response time, documents requested, decision and reasons.
10. Policy versioning and change management
What. Major policy changes are versioned and dated, the page footer reflects the last-updated date and the Vendor Agreement carries an explicit version constant (current: v3-2026-05-30) that triggers vendors to re-accept on the next dashboard login. Internal review by the marketplace team precedes publication. External legal counsel review by a Sri Lankan commercial lawyer is not a current control; we will commission such review when commercial scale, regulatory risk, or specific transaction patterns warrant the spend. Buyers and vendors who want the rationale for any specific clause can request it at info@harker.international.
Evidence retained. Policy version history (git), change log, internal-review notes, vendor re-acceptance log.
Honest scope note. Some of these controls are currently operated manually by a small team during the marketplace’s ramp. The per-certificate status data model, status pills, and the daily expiry-digest cron are live as of 2026-05-30. Vendor self-service editing inside the WCFM dashboard and full automation of vendor onboarding state transitions are the next milestones. We publish the framework so vendors and buyers can hold us to it as we build out the supporting technology.