Factory Owners: Cost Sheets, Client Lists & Accio Work Data Red Lines
Public listing attributes, published storefront price tiers, and sanitized RFQs may enter Accio Work L1 draft workflows. Bottom pricing, client rosters, and unreleased certification scans must remain in ACL-secured cost archives. Local-First architecture is an engineering claim, not a third-party GDPR or ISO certificate. Complete the executive safety checklist before enabling browser automation. Publishing, price changes, and Trade Assurance sign-offs must remain strictly human-operated. Accio Work is not Gold Supplier AI.
This executive guide is written for factory owners, CPOs, pricing directors, and quality managers: once Accio Work is installed across company hardware, which business assets may enter chat prompts, draft folders, and Skills, and which must remain strictly locked in access-controlled repositories. Permissions and compute allocation are detailed in E01 Budget ROI.
Accio Work connects to your active, running Alibaba.com storefront. Data governance rules apply universally regardless of corporate jurisdiction. Storefront eligibility and corporate structuring are detailed in our Hong Kong Eligibility Guide.
1. Define Red Lines Before Enabling Automation
Factory executives frequently misinterpret 'the Agent can process local files' as 'upload all internal price sheets, client books, and test files so the Agent gets smarter'. The inevitable consequence: bottom cost figures appear in listing draft titles, historical client mobile numbers leak into group chat logs, and unreleased lab reports are falsely drafted as 'Already certified'.
| Governance Layer | Core Managerial Scope | Scope & Reference Guide |
|---|---|---|
| Authorization | Master account custody, L0–L3 approval gates, sub-account limits | Detailed in E01; supplemented here by data tiers |
| Compute Budget | 500 trial credits, AWB tiers (Starter / Standard / Flagship) | Official rate card on /en/pricing |
| Data Red Lines | Cost sheets, BOMs, client rosters, audit scans, screenshots, exports | Core focus of this guide |
| Fulfillment Capital | Trade Assurance orders, settlement account updates, refunds | Strictly manual, see Trade Assurance |
| Stack Purchases | Gold Supplier vs. Verified, P4P ad spend, Accio Work stack | See E03; unbundled independent invoicing |
1. Do we maintain an isolated cost folder with strict ACL access limited only to named pricing directors?
2. Do all task prompts mandate stop conditions: 'do not publish, do not send messages, do not alter prices, do not access cost folders'?
3. Are client chat exports and full rosters sanitized before entering draft workflows?
4. Are agency computers strictly barred from master credentials and bottom-cost files?
5. Do we acknowledge that Local-First is an architectural claim, not a GDPR certificate or zero-risk guarantee?
2. Three Permitted Data Classes for Accio Work
The golden rule: Publicly available data, or data vetted for public release, may enter L1 drafts; unreleased commercial secrets may never enter. Accio buyer search algorithms index text listing attributes, not internal hard drives.
| Permitted Class | Typical Examples | Ingestion Method | Auditor | Mandatory Stop Condition |
|---|---|---|---|---|
| Public Listing Fields | Materials, dimensions, MOQ, lead times, ports, published certificates | Text copy or read-only extraction, no full-page screenshots | Ops + Quality | Do not publish, do not change live price |
| Published Prices | Front-end FOB tiers matching active live listings | Feed exact front-end figures only | Pricing Lead | Never append internal cost columns |
| Sanitized RFQs | Specs, volume, cert requests; stripped of buyer names, phones, target bids | Manual sanitization before drafting reply skeletons | Sales Lead | Do not send reply, do not add WhatsApp |
3. Cost Folders & Mandatory ACL Access Control
A 'cost folder' is not a casual desktop directory—it is a secure, access-controlled repository (ACL) on company NAS or encrypted enterprise storage with named account auditing. The following items must never enter Accio Work:
1. Bottom Costs & Margins: Expose pricing floor and destroy negotiation leverage. Restricted to Owner & Pricing Lead.
2. Internal BOMs & Labor Cycles: Proprietary manufacturing formulas. Restricted to Plant Director.
3. Client Roster & Historical Deal Prices: Risk of client poaching and non-disclosure violations.
4. Unreleased Lab Reports & Factory Blueprints: Never expose pre-audit materials to automated model contexts.
5. Banking Credentials & Trade Assurance Settings: Fulfillment lifeblood. L3 strictly forbidden.
6. Passports & Tenancy Leases: Corporate KYC documents, not operational listing copy.
4. Physical Separation of Public vs. Cost Pricing
Sales reps frequently keep single spreadsheets containing SKU, front-end price, bottom cost, margin, and client name in adjacent columns, then screenshot the entire sheet for the Agent. Vision models parse all visible text indiscriminately.
| File Name & Type | Storage Location & ACL | Permitted Column Attributes | Authorized User |
|---|---|---|---|
| public-listing-prices.xlsx | Operations shared drive, accessible to L1 | SKU, published tier prices, MOQ, FOB port | Sales Rep + Agent Drafts |
| cost-sheet.xlsx | Cost Archive, strict ACL lockdown | Bottom cost, BOM, labor, margin, supplier code | Pricing Director (Human only) |
| pi-draft.docx | Drafts repository / Local staging | Prices strictly matching public rate sheet | Sales Manager sign-off |
5. Client Lists & Chat Export Sanitization
Never feed complete customer rosters or 3-year raw WhatsApp/WeChat chat histories into Agent prompts. Execute manual sanitization: strip names, phones, emails, and historical concessions, retaining only technical specs, requested volumes, and target delivery ports.
6. Certificates & 'Available' Compliance Phrasing
Verified Supplier factory audits cross-reference certification statements on listing pages. If an Agent misconstrues 'CE assistance available' as 'Already certified', the audit will fail. Only verified certificate numbers may enter listing copy; pending standards must be marked 'Not available'.
7. Screenshots Are Not Safe Text
Multi-modal vision models extract OCR text with high fidelity. Cropping or mosaic masking frequently leaves adjacent margin columns readable or creates excessive image compute burn. Mandate clean plain text extraction.
8. Agency Hardware Governance & Credential Isolation
Production store credentials and internal cost files must remain exclusively on enterprise hardware. Agencies may build Skills and deliver training, but must never hold master passwords or run unsupervised browser automation against production stores.
9. Local-First Architecture vs. Third-Party Certification
Accio Work's Local-First model indicates client-side execution and no retraining on customer data. This is an engineering design, not a third-party GDPR or ISO 27001 certificate. Enterprise security requires internal ACLs, not reliance on marketing claims.
10. BOM Pasting in Group Chat Channels
Integrating Agents into DingTalk or enterprise chat groups creates severe leakage risks if employees paste BOM tables into chat contexts. Prohibit default '@all' Agent triggers and restrict Agent bot channels to sanitized inquiry workflows.
11. Pre-Automation Executive Checklist (12 Checkpoints)
Executives must audit the 12-point safety checklist before activating browser automation: verify target domains, confirm stop conditions, isolate master accounts, audit active cost sheets, and confirm that human supervisors are physically on-duty.
12. Red Team Factory Pitfalls (10 Practical Case Studies)
Review 10 real-world manufacturing failure modes: leaking bottom costs in quote drafts, exporting 3-year raw WhatsApp records, vision OCR extracting margin columns, and agency overnight automation accessing network storage.
13. Two-Week Security Pilot Calendar
Structured 14-day schedule: Days 1–2 set ACLs and run L0 read-only tests; Days 3–5 draft single-SKU public fields; Days 6–8 classify sanitized RFQs; Days 9–10 execute red-team self-audits; Day 14 host the renewal gate requiring zero security infractions.
14. Two Manufacturing Case Scenarios
Hardware Manufacturer (Running Store, Local Cost Sheet): Owner acts as master admin, sales manager extracts public pricing, 500 trial credits spent purely on L0 reconciliation and L1 draft creation.
Lighting Manufacturer (Full Certificate Library, Heavy Chat Usage): Quality lead provides single-line compliance text; sales team sanitizes buyer inquiries; production chat channels strictly bar AI bots.
15. Layering Authorization & Trade Assurance Governance
Align L0 (Read-Only), L1 (Drafting), L2 (Human Sign-Off), and L3 (Strictly Prohibited). Trade Assurance orders, delivery sign-offs, and bank modifications remain permanently under L3 manual control.
16. Corpable Scope of Service
Corpable Marketing Limited (aliad.hk) provides: Genuine Accio Work licensing, enterprise SOP implementation, and Skill package integration. Senior Advisor Mr. Chan. Office: Chevalier House, 45–51 Chatham Road South, Tsim Sha Tsui, Hong Kong.
Contact: /en/pricing · /en/contact.
17. Frequently Asked Questions
Can bottom cost pricing be fed into Accio Work?
No. Bottom costs, gross margins, and internal factory BOM data must remain strictly in access-controlled (ACL) cost folders accessible only by designated pricing directors. Only publicly published or pre-approved public listing attributes, front-end prices, and sanitized RFQs may enter L1 draft generation. Local-First architecture does not equal zero risk. Accio Work is not Gold Supplier AI.
Can client lists and WeChat chat logs be uploaded to AI Agents?
No. Complete client rosters, exported chat logs, personal phone numbers, and private price negotiations cannot be dumped into Accio Work. Inquiry data must first undergo manual sanitization to strip names, contact info, and private concessions, retaining only technical specs, quantities, certifications, and delivery timelines before entering L1 drafts. Group chat Agent integration is subject to the same strict red line.
Can unreleased audit scans and test reports be used for Agent listing creation?
No. Original certificates, unreleased audit scans, and full laboratory test reports must remain strictly in quality archives. Agents can only reference published standard names and verified certificate numbers. If a standard is pending, it must be marked 'Not available', strictly prohibiting Agents from phrasing 'facilitation possible' as 'Already certified'.
Does Local-First mean zero data egress and official GDPR certification?
No. Accio and Corpable market Local-First architecture: local file parsing and browser automation execute on enterprise client hardware, and enterprise data is not used for public model retraining. This is an architectural product claim, not a third-party GDPR, ISO 27001, or SOC 2 certificate. Screenshots, clipboard pasting, group chats, agency computers, and browser navigation to cost dashboards can still expose data beyond local perimeters.
Can agency or outsourced computers run Accio Work connected to production stores?
No. Production store authorization and cost folders must remain strictly on internal company hardware. Agencies may assist with Skill development, prompt design, and training, but cannot hold master storefront credentials or access internal bottom-price cost sheets. Once browser automation is enabled on agency hardware, the Agent can inspect everything accessible in that browser session.
Is sharing screenshots with Agents safer than pasting spreadsheet tables?
In most cases, it is far more dangerous. Multi-modal vision models extract OCR text and numeric values directly from image pixels. Quote screenshots frequently contain hidden cost columns, margin figures, and client names. Safe practice requires manually extracting public fields into plain text, avoiding full-table screenshots or dragging cost spreadsheets into chat windows.
What must business owners check before enabling browser automation?
Inspect active browser tabs: ensure they are limited to public listings or inquiry queues, never cost spreadsheets, ERP systems, banking portals, Trade Assurance settlement pages, or chat exports. Cost-related pages are forbidden by default. Task prompts must mandate explicit stop conditions: do not publish, do not send messages, do not alter prices, do not place orders, and do not access cost folders. Disable automation whenever human supervisors are off-duty.
Is data governance the same as purchasing Accio Work or upgrading to Verified Supplier?
No. This guide strictly delineates data boundaries for AI Agents. Store authorization and compute budgets are covered in E01. Verified Supplier, P4P ads, and Accio Work add-on purchases are detailed in E03. Corporate entity registration is covered in dedicated storefront setup guides. Accio Work connects to your active running store regardless of jurisdiction.
18. Next Steps & Executive Action
- Designate cost archive paths and establish explicit ACL rosters.
- Print the permitted/prohibited data matrix and require pricing director sign-off.
- Pilot 500 trial credits strictly on public fields and sanitized RFQs.
- Ensure agency computers have zero master credentials and zero cost access.
- Mandate human execution for all Trade Assurance orders and price changes.
- Contact Corpable's Senior Advisor Mr. Chan for official enterprise licensing.
