The store script (code) in an AI store
An AI store can have its own code for anything a design alone can't do: a sliding product rail, a quick-view window, a hover effect that shows the back of a product, a size picker on a card, a custom cart drawer, scroll animations. The AI writes it in one file, the Store script, which runs on every page of the store.
You always see when code changes: whenever a change adds or edits the store script, the AI's answer shows "This change adds code that runs in your shoppers' browsers" with View code to read exactly what was written. Ordexs detects this itself; it doesn't depend on the AI saying so. Review it before you publish, like any other change.
What the code can and can't do: it reads your store's live data (products, prices, stock, cart) and can add to the cart or open the order form. It can't set what an order costs: Ordexs prices every order again from your products and delivery settings when it is placed. If code touches what the order form shows or sends (its prices, total, fields or Order button), the form check under the AI's answer says so, and Publish asks you to confirm, or refuses if shoppers could no longer order (see "The order form, cart and checkout in an AI store"). It can't reach your dashboard, your account or other stores.
Where it can send things: an AI store only talks to Ordexs, Google Fonts, YouTube/Vimeo, the bot check and the ad pixels you connected in Integrations. For anything else the code needs (a chat widget, another analytics tool), allow its address in Settings → Domains → Outside services first; the AI tells you which address when a design needs one.
You are responsible for the code on your store, as on any platform: if you ask for something you don't understand, ask the AI to explain it before publishing.