LocalizeASO Logo LocalizeASO

Review and submit

LocalizeASO separates generation from submit and scheduling. Agents create reviewable proposals; a human must approve before Figma apply, metadata draft apply, pricing schedule, status changes, or App Store Connect submit.

Agent Pass users can keep App Store Connect credentials local and use exported asc handoffs after approval. Hosted LocalizeASO submit convenience requires connected ASC credentials and a pass that includes hosted submit.

Metadata submit

Approved metadata can be applied to LocalizeASO drafts first. Hosted passes can then submit those reviewed drafts through an App Store Connect job; Agent Pass users can export canonical asc metadata files and submit locally.

Submit jobs return:

  • Job ID.
  • Status.
  • Per-locale results.
  • Errors for partial or failed locale updates.

Dry run

Use dry run when you want to verify payloads and locale coverage before writing to App Store Connect.

Completion notifications

Long-running submit or schedule jobs can request a browser completion notification. The dashboard polls job status and notifies when the job completes or fails.

Release notes submit

Release notes can be submitted separately from the main metadata workflow. This is useful when only the version notes change.

Screenshot handoff

Approved screenshot copy is applied back into the matching Figma file after human confirmation. Upload the final screenshot assets through a human-run workflow such as hosted LocalizeASO submit convenience, local asc, Transporter, or your existing release pipeline. Hosted screenshot upload and ordering must reference the applied review job and approved apply-plan fingerprint; screenshot ordering can then be submitted from the dashboard when ASC is connected.

Pricing schedule

Pricing review produces approved territory price changes first. Hosted passes can schedule them through LocalizeASO pricing jobs; Agent Pass users can export JSON or an asc CSV payload and schedule locally. Hosted jobs report progress by territory and separate updated, unchanged, and failed results.

Before Submit

Check these before applying, scheduling, or submitting:

  • App Store Connect credentials are valid when using hosted submit convenience.
  • Local asc credentials and target app ids are correct when using BYO handoffs.
  • The selected app and platform are correct.
  • The app version is editable.
  • Metadata field limits pass validation.
  • Keywords do not duplicate title or subtitle terms unnecessarily.
  • Screenshot sets have the expected device sizes.
  • Pricing start date is correct.
  • The approved review job matches the app, Figma file, proposal, and locale/territory scope you are about to apply or submit.