Q&A v1.0 · Authoritative reference for customers and internal onboarding
FAOS is an internal operations system designed to manage orders, purchase orders, and invoices with clear controls and traceable records. It focuses on reducing manual mistakes and operational chaos in document-heavy B2B workflows.
🔗 Product overview / entry point
→ Landing
FAOS is not a retail POS system, an e-commerce checkout, or a tax or audit submission platform. We provide structured records, operational controls, and audit logs — not statutory filings or audit opinions.
🔗 Terms & scope reference
→ Terms
→ Compliance
All data is isolated at the company level and enforced on the server side. Clients cannot specify or impersonate another company through requests.
🔗 Security & architecture summary
→ Security
→ Architecture
"Audit" in FAOS refers to audit trail and auditability, not statutory audit. FAOS records critical operational actions such as exports and configuration changes to support internal review and external audit processes.
🔗 Audit log explanation
→ Audit logs
FAOS applies layered controls to reduce attack surfaces and limits the impact to a single company context. Critical actions remain traceable through audit logs.
🔗 Risk & incident handling
→ Risk controls
Register through the landing page to create a company workspace. After registration, the system will guide you to complete company profile information.
🔗 Register
→ Sign up
Company information is used to generate orders, PO, invoices, and records. Missing information may block certain actions by design to prevent downstream errors.
🔗 Company profile requirements
→ Company profile
Yes. Companies can invite multiple users and assign roles with different access levels.
🔗 User & role management
→ Users and roles
FAOS sends emails using your own company email account, ensuring messages originate from your business, not a third-party sender.
🔗 Email system overview
→ Email system
Email settings are managed in: Office → Settings → Email.
🔗 Direct link (after login):
→ Email settings
An App Password is a provider-generated credential that allows third-party systems to send emails securely on your behalf.
🔗 App Password guide
→ App passwords
If your email provider supports OAuth, it is recommended. If not, App Passwords are a secure and commonly accepted alternative.
🔗 OAuth vs App Password comparison
→ Email auth options
Actions may be blocked when required information is missing, approvals are incomplete, or permissions are insufficient. This is an intentional design to prevent errors from propagating.
🔗 Blocking rules & validations
→ Operational controls
Exports are considered high-risk operations. FAOS records export activities to support accountability and review.
🔗 Export logging policy
→ Export logs
FAOS provides standardized operational controls. Organizations requiring highly customized workflows or statutory compliance automation may not be suitable for this system.
🔗 Who FAOS is for / not for
→ Fit and scope
A: The system is enforcing Iron FIFO logic.
A: This indicates your current plan does not include WMS Execution Seats, or your WMS Module activation has expired. Please check your Quota Overview in Office.
A: This is the Iron FIFO logic in action. The system has identified a more senior (older) stock batch that must be shipped first to ensure inventory freshness. Consult Atlas AI for specific batch details.
A: All returns must enter the Quarantine zone.
A: Under the delivery evidence model (V11)...
A: The system is enforcing Iron FIFO logic.
A: All returns must enter the Quarantine zone.
A: Under the delivery evidence model (V11)...
All contractual and legal definitions are governed by canonical legal pages.
🔗
→ Legal hub (Malaysia jurisdiction summary)
→ Terms of Service
→ Privacy Policy
→ Refund Policy
FAOS binds documents to company master data rules, but you remain responsible for approving commercial terms and confirming payloads before issuance. See Terms §36 for verification duties and limitations.
No. WMS tooling models your execution and evidence; carriers, dispatch, insurance, customs, and final risk decisions belong to your organization and counterparties unless separately contracted offline.
Transactional messaging may traverse customer-configured SMTP and DNS reputational posture. If Google Workspace, Microsoft 365, or other providers classify messages as queued, deferred, bounced, quarantined, or spam, Orbita does not guarantee inbox placement — validate templates, DNS records, quotas, attachments, recipient allow-lists, and retry policies on your tenant.
End of Guide