GingerOSTrade compliance for IT
One layer over your ERPs.
GingerOS reads what compliance needs from the systems you have, starting with exports you already produce. We run it and maintain the connectors, and your master data stays where it is.
- Give compliance the data
About one a weekNoneIllustrative - Keep data under your policy
3 to 5NoneIllustrative - Know who changed a field
NoneEvery field GingerOS managesIllustrative
A window listing the three IT jobs on this page: giving compliance the data, keeping data under your policy and knowing who changed a field. Each row shows today’s value struck through next to the GingerOS value, marked Illustrative, not measured.
Give compliance the data.
Exports first, then read-only access, one system at a time. We maintain it.
Illustration with sample data: an old-style service desk queue of five requests to IT from compliance, legal and a broker, such as an HS export from three ERPs and three years of entries from nine broker portals. Two requests are flagged as stale, and a pinned comment marks the one that has waited 19 days on IT.
Illustration with sample data: a GingerOS list of four data sources with how each arrives, its access, an owner and a status: ERP exports and forwarder reports as files you send, both connected, then the ERP read-only by API as next and PLM as later. Below it: no master data migrated, connectors maintained by GingerControl, new logins for reviewers only.
Every notice brings a ticket: pull HS codes from three ERPs, by Monday.
Ad-hoc export requests to IT
Illustrative
Illustrative comparison, not a measured result: ad-hoc export requests to IT, about one a week today against none with GingerOS.
Keep data where policy says.
Only the fields a decision needs leave the source system.
Illustration with sample data: an old-style shared folder of specs and costed BOMs with duplicate copies, where a pinned comment points out that a confidential formula PDF now also sits with the broker. The status bar says the folder is shared with 14 people, 3 outside the company.
Illustration with sample data: a GingerOS data policy window with three places it can run, your VPC selected, and what each role sees. For one sample part the formula stays in R&D and only an aluminum share of 60 to 70% is answered.
Specs and costed BOMs travel as attachments, and copies pile up everywhere.
Sensitive files emailed per request
Illustrative
Illustrative comparison, not a measured result: sensitive files emailed per request, 3 to 5 today against none with GingerOS.
See who changed a field, and why.
Every HS and origin value has an owner and a log. The ERP field is a copy.
Illustration with sample data: an old-style spreadsheet of four changes to HS code fields, made by a batch migration, a user who has left and a portal sync, with the Reason column empty in every row. A pinned comment says there is no reason and the person has left.
Illustration with sample data: a GingerOS field history for one sample part’s HS code, with its owner, current value and three dated events. Each shows who acted and why: approved for a new ERP item, rechecked after a Section 232 notice, then written to the ERP.
The HS code is a field with no version, no reason and no owner.
HS and origin fields with an owner and a log
Illustrative
Illustrative comparison, not a measured result: HS and origin fields with an owner and a log, none today against every field GingerOS manages, drawn as two bars.
Numbers marked Illustrative are not measured results. Your own baseline is set with you before the build.
Questions you’ll probably ask
How many interfaces, and who maintains them?
One read-only layer, connected in stages, one system at a time. We build and maintain the connectors; you keep a named owner for each field.
Do you need write access or ERP customization?
Not on day one, and not for the prototype. If approved values should go back into the ERP, IT approves each field once through your change management, and compliance approves each value. Anything inside your ERP screens, like a warning on the PO, is scoped with IT at kickoff. No master data is migrated.
Is this a new system of record?
For HS codes, origin and the reasoning behind them, yes. We run and maintain it, and it belongs in your access and vendor reviews like any other system.
What does IT have to do for the prototype?
Nothing. The Prototype Week needs about ten sample part numbers, no system access and nothing installed. If you like, IT can start the security review the same week.
Do you train AI models on our data?
No. We never use your data to train AI models, and how your data is used is written into the contract.
Where does it run, and how is it secured?
Data is encrypted in transit and at rest, and access is by role. Where it runs, our cloud in a region you choose, your own cloud or on premises, is agreed with your IT before you sign.
What does your security review cover?
Before you sign, we answer your IT’s review: where it runs, how data flows, which AI model providers see which data, who on our side can access it, and how people sign in.
What happens to our data if we leave?
Every record exports by CSV and through the API, in formats you can read without us.
