Quick answer: EA says there is no official mod support planned for STAR WARS Zero Company. That means there is no developer-supported mod SDK/API or compatibility promise at present.
No official mod support
The launch FAQ explicitly says the team respects the modding community but has no official mod support planned. This is a current support-policy statement, not proof that community users cannot alter local files.
Community mods are different
Unofficial mods can still appear for PC games without official support. They may use file replacement, configuration edits or memory tools. Because those methods are not supported, a game patch can break them without warning.
Do not confuse trainers with mods
A trainer or Cheat Engine table changes a running game's memory and is not the same thing as a supported content mod. Searches for "mods" often mix cosmetic changes, save edits and cheat utilities together. Keep those categories separate so users understand the risk.
Safer modding practice if community tools emerge
Back up saves, keep the original game files recoverable, install one modification at a time, verify compatibility with the exact game build and use storefront file verification to return to a clean state. Do not download modified executables from sources you do not trust.
Will official support arrive later?
No announcement currently says it will. If Bit Reactor or EA publishes a mod toolkit or policy later, that official update should replace this status page's current answer.
What "no official support" changes for players
Without an official toolkit, mod authors cannot rely on a documented extension API, stable data schema or compatibility layer promised by Bit Reactor. Instructions can therefore become obsolete after patches, and two modifications that touch the same files may conflict. Troubleshooting also starts by reproducing the problem on an unmodified installation because official support cannot reasonably diagnose every community alteration.
What to watch for after updates
If a community ecosystem grows, check each mod's stated game version before launching after a patch. Cosmetic file replacements, configuration edits and gameplay changes can have very different failure modes. Keep a list of what you changed so reverting is deterministic rather than guessing which file caused a crash.