Upload cartridge code from VS Code to the code version selected on your active SFCC connection. Use a manual upload for an explicit deployment, or enable auto upload while developing to synchronize saved cartridge changes.
Choose the deployment target
- Add and select your development sandbox in Connections.
- Confirm the sandbox hostname and selected Code Version before uploading.
- Link the local cartridges you work on with Cartridge Management.
Local cartridge links help the editor resolve your project. Linking a folder does not deploy it or change the site's server-side cartridge path. Keep the site's cartridge order aligned with the implementation you intend to run.
Upload on demand
Open the Command Palette and run B2C - Upload to Active Instance. The extension packages code for the active instance, uploads it, and extracts the uploaded archive on the sandbox. Wait for completion before testing the changed storefront route.
If the upload fails, inspect the extension's output and the reported error. Confirm the connection, code version, access permissions, and network connectivity before retrying.
Synchronize saved changes
Use the auto upload control in the status bar for the active connection. Auto Upload Enabled means the watcher can upload cartridge changes as you save them. Toggle it off when you want to make local edits without synchronizing them to that sandbox.
Auto upload follows the selected connection. Check the target again when switching sandboxes or code versions, and use the status bar to confirm whether automatic synchronization is enabled.
TypeScript projects
SFCC executes the generated server-side JavaScript. Make sure your transpilation workflow produces the JavaScript you intend to upload; saving a TypeScript source file alone is not a substitute for compiling it. See TypeScript transpilation and CI/CD.
Verify the result
Run the affected storefront route or job against the selected development sandbox. If the old behavior remains, check the active code version, the site's cartridge order, and whether the expected file was uploaded. For step-through inspection, continue with Debugging.