One SKU. One truth.

Buy side is what you pay your manufacturers — per-supplier, per-product cost with volume tiers, MOQ, lead time, and validity periods. Sell side is what you charge your clients — per-client, per-product price with volume tiers and effective dates. Margin is computed live from both sides. The Economics sub-tab adds freight share and duty share to compute landed cost, which is the real margin basis. Separating them means Sales can see sell prices without seeing manufacturer cost (RBAC field-level restriction), and Finance can see the complete picture.

No — the Sales role has field-level RBAC restrictions on the pricing tables. Sales sees the Sell Side sub-tab and the client pricing matrix, but the Buy Side sub-tab and the manufacturer cost column on any product detail page are hidden. Admin, Manager, and Finance roles see everything. Ops sees specifications but no pricing. The Viewer role sees the catalog only. Margin is therefore visible to Sales as a percentage (so they can negotiate) but not as a dollar buy-cost they could reverse-engineer.

The Requirements Matrix sub-tab maps product category × destination country → required certificates. Set up once during onboarding (e.g., medical gloves shipped to EU require CE 2865 and EN 455-3; shipped to US require FDA 510(k) and ASTM D6978). When an order is created with a destination market, the system automatically checks every product line against that market's requirements and surfaces missing or expired certificates as warnings before the order ships. The mapping is configurable per destination and per category — operators can add new markets and requirements at any time.

Certificates expiring within 90 days surface as amber in the Compliance KPI and on every affected product's detail page. Expired certs surface as red. The system also fires task notifications to the user responsible for compliance (configurable in Settings). Critically, an expired or missing cert does NOT block an order from being placed — the operator may have a replacement in progress or an exemption. It just makes the risk visible at every relevant touchpoint: the order detail page, the shipment manifest, and the compliance dashboard.

Yes. The Import Products flow accepts CSV upload with column mapping — the importer detects your column headers and lets you map them to EDMA fields (Name, SKU, Category, Variants, HS Code, Unit Weight, CBM, etc.). Duplicate SKUs are rejected with row-level errors so you can fix them in the source and re-upload. After import, you can bulk-add manufacturer prices, client prices, and warehouse inventory through the same CSV mechanism. Most operators are fully set up within an afternoon. The data dictionary and a sample CSV are available in the Help Center.