SuiteCommerce Developer study plan

Map the SuiteCommerce architecture layers (Commerce Web Store, Site Builder, SSP applications, SuiteScript backend) and draw a diagram showing how a product detail page request flows end to end

Explain the difference between the SuiteCommerce (SCA) and SuiteCommerce Advanced (SCA/SSP) application models and identify which one a given deployment uses from configuration alone

List the core record types involved in a storefront (items, pricing, customers, sales orders, site configuration) and note which are read at runtime versus cached

Set up a personal study sandbox or documentation notebook and log every architecture term you cannot yet define in your own words

Trace how a storefront request moves from the CDN/NetSuite hosting layer through the application router to a backend service and back

Identify where caching (page, fragment, and record-level) applies and predict which changes require a cache invalidation step

Compare the extension points available at the platform level (configuration, templates, services, SuiteScript endpoints) and choose the right one for three sample requirements

Write down the security and permission model for storefront access, including how shopper sessions and customer records are linked

Write SuiteScript 2.x modules using define/require and the correct entry point annotations, and verify each deploys without error

Implement a RESTlet or Suitelet endpoint intended for storefront consumption and handle authentication and error responses explicitly

Use search and record modules to read item and pricing data efficiently, avoiding per-record loops where a single search suffices

Apply governance awareness: estimate usage units for a script and restructure one script that would exceed limits

Add structured logging and try/catch handling so failures surface actionable messages

Connect a frontend call to your backend endpoint and confirm the data contract (request shape, response shape, error shape) end to end

Implement user-event and client-side script hooks where the platform expects them and explain when each fires

Handle asynchronous behavior correctly: loading states, retries, and failure messaging in the UI

Document the integration contract so another developer could consume the endpoint without reading your code

Configure a Site Builder site: domain, touchpoints, catalog and category presentation, and theme selection, then verify each setting takes effect

Explain how themes, skins, and extensions relate and identify which layer to change for a given visual requirement

Customize templates and layout without breaking the base theme, using the supported override mechanism

Set up content types (landing pages, product lists, carousels) and confirm they render in the expected touchpoints

Build a theme extension that adds a new template and a new frontend module without editing core files

Use the frontend module system (module definition, dependencies, entry point) to add interactive behavior to a product or cart page

Implement a client-side call to a backend service and handle the response in the UI, including a no-data state

Verify the customization survives a theme update by testing in a clean environment or documenting the upgrade path

Optimize a storefront page: reduce unnecessary requests, defer non-critical scripts, and measure the before/after difference

Implement a checkout or cart interaction that respects the platform's state model rather than duplicating it client-side

Review your work against accessibility and responsive layout expectations and fix at least three issues found

Revisit the week 1 architecture diagram and correct anything your hands-on work proved wrong

Build a timed practice set weighted 25/25/25/25 across the four domains and record a score per domain

Re-study only the two weakest domains using your own glossary and notes rather than new material

Explain aloud, without notes, how a full storefront request flows and where each customization layer intervenes

Assemble a one-page exam-day reference of concepts you repeatedly miss