WooCommerce NZ address autocomplete

Current status

StreetKit still ships the hosted JavaScript widget and selected New Zealand address data as the current public product. A WooCommerce-specific plugin now exists as a beta preview under plugins/woocommerce/streetkit-woocommerce, with a local beta package path of dist-plugins/streetkit-woocommerce-0.1.0-beta.zip.

The beta plugin should be used on staging stores and controlled test installs only. It is not a stable release, does not have a public download link on this site, and should not be described as production-ready until real WordPress/WooCommerce checkout QA has passed. Rebuild the beta ZIP from the current repository checkout before installing it, so the package matches the source under review.

Current beta release notes and support policy live in the StreetKit repository docs. They keep the public position at 0.1.0-beta, manual install, staging-only testing, no production-supported checkout type, and no Checkout Blocks support claim until matching release evidence exists.

Why autocomplete helps checkout

Install beta ZIP

If you are working from a StreetKit repository checkout, build the beta ZIP from the repository root:

pnpm run streetkit:woocommerce:package

Upload dist-plugins/streetkit-woocommerce-0.1.0-beta.zip to a staging WordPress admin through Plugins > Add New > Upload Plugin, then activate StreetKit for WooCommerce.

• Current beta version: 0.1.0-beta.
• The package is for manual controlled testing, not public production rollout.
• There is no WordPress.org listing and no WooCommerce Marketplace listing.
• This site intentionally does not publish a fake download URL.

Admin settings

After activation, open WooCommerce > StreetKit. If WooCommerce is inactive, the beta exposes the same settings under WordPress Settings > StreetKit so activation remains safe.

• Enable StreetKit only when you are ready to test checkout autocomplete.
• Choose public mode for anonymous evaluation, or enter an issued public siteId for registered testing.
• Use a siteId shaped like sk_live_... or sk_test_...; it is public identification, not a secret.
• Keep the index base URL on an https://index.streetkit.smp.kiwi public or registered v1 URL supplied for the beta.
• Keep New Zealand only enabled unless a future release documents other countries.
• Enable billing and shipping autocomplete independently.
• Leave metadata storage off unless you deliberately want selected-address metadata on classic checkout orders.
• Use debug mode only for non-sensitive provider diagnostics.

Public mode and siteId

Public mode uses the StreetKit public static index for evaluation and low-volume testing. It does not require a siteId and does not create a merchant account, API key, or private quota.

Registered testing uses an issued public siteId. The siteId is browser-visible identification, not a secret. Do not put names, email addresses, domains, order IDs, customer IDs, account IDs, passwords, or API keys in the value.

StreetKit should receive only the address query needed for autocomplete and static index requests from the provider path. It should not receive full checkout payloads or contact, cart, payment, or order data.

Checkout behaviour

Address mapping and metadata

The beta provider maps a selected StreetKit address into the WooCommerce provider address object. address_1 uses structured street number and street data where available, address_2 stores level/unit data, city prefers the selected city with suburb fallback, state is blank by default, postcode is only copied when present, and country is NZ.

Optional metadata storage is off by default. When enabled on classic checkout, the beta can save allowlisted StreetKit selected-address metadata such as selected address ID, selected label, latitude, longitude, and source version through WooCommerce order APIs. Query text, names, email addresses, phone numbers, cart data, payment data, order IDs, customer IDs, account IDs, and whole checkout payloads are not stored as StreetKit metadata.

The selected address label may be personal address data once it is stored on an order. Treat it under the store's normal WooCommerce privacy and retention controls.

Classic and Block checkout status

• Classic shortcode checkout provider integration and optional selected-address metadata hooks are implemented for beta testing.
• Classic checkout has not been manually QA-tested on a live WordPress/WooCommerce store from this repository.
• Only provider diagnostics exist for Checkout Blocks; real Checkout block search, selection, field population, order placement, and metadata persistence have not been manually tested.
• Do not claim Checkout Blocks support. Blocks metadata persistence is not implemented or claimed.

Troubleshooting

• If no settings page appears under WooCommerce, confirm WooCommerce is active; otherwise check Settings > StreetKit.
• If checkout shows no suggestions, confirm StreetKit is enabled, billing or shipping autocomplete is enabled, the country is NZ, and the query has at least three meaningful characters.
• If the provider remains inactive, confirm the installed WooCommerce version exposes the address autocomplete provider API.
• If registered testing fails, confirm the siteId is issued, public-mode settings match the beta instructions, and the static index URL is reachable.
• If registered mode is selected with no valid siteId, StreetKit checkout autocomplete stays inactive and manual WooCommerce address entry remains available.
• If metadata is missing, confirm metadata storage is enabled and the test is classic checkout; Blocks metadata storage remains pending.
• If StreetKit requests fail or time out, checkout must still allow manual address entry and order placement through WooCommerce.

Support policy and reporting

The current beta support boundary is classic shortcode checkout provider integration on staging stores. No production checkout type is supported yet, because release evidence and release-owner sign-off are missing. Checkout Blocks are untested and not claimed.

• StreetKit can investigate package install, version alignment, settings, provider registration, classic checkout beta behaviour, privacy, and fail-open issues.
• Production incident response, store-specific theme or checkout customization debugging, payment gateway behaviour, shipping rules, taxes, fulfilment rules, and unsupported Blocks claims are outside the beta support boundary.
• Report beta feedback through the StreetKit contact page with the plugin version, ZIP filename, WordPress/WooCommerce/PHP versions, theme, checkout type, access mode, redacted steps to reproduce, and whether manual address entry and order placement still worked.
• Do not send real customer data, production payment credentials, cookies, secrets, full checkout payloads, request captures, or unredacted order screenshots.