Southeast Asia carrier coverage — proposing a Thai carrier connector

[Simon Isara (simon-isara)]

Looking through modules/connectors/ and community/plugins/, I don't see any Southeast Asian carriers represented. Coverage is strong across Europe, North America, and Australia/NZ, but Thailand's main carriers — Flash Express, Thailand Post, J&T Thailand, Kerry Express — aren't in either tree.

I'm Thai and work with these carriers, so I'd like to contribute a connector. Before I start, I want to make sure I build it where and how you'd want it.

I've read CARRIER_INTEGRATION_GUIDE.md and plan to use sdk add-extension rather than copying an existing plugin by hand, then follow the standard structure — providers/mappers split, schemas generated via run-generate-on, tests modelled on community/plugins/zoom2u/tests/.

Three questions:

1. Placement. The guide distinguishes direct carriers (modules/connectors/) from hub carriers (community/plugins/). Thai carriers like Flash Express are direct carriers, but I'd assume a new unproven contribution should start in community/plugins/. Which would you prefer?

2. Scope. These carriers gate rating and shipment creation behind a merchant contract, but tracking endpoints are more accessible. Is a tracking-only connector acceptable, or would you want the other operations stubbed or raising NotImplementedError? Is there an existing partial connector I should follow for that?

3. Direct vs aggregator. If direct carrier credentials turn out to be a blocker, an alternative would be a tracking aggregator that covers Thai carriers, similar in shape to the existing easyship and easypost hub plugins. Would that be useful to the project, or do you prefer direct carrier integrations?

Happy to follow whatever structure you'd like. If there's an existing plan or someone already working on SEA coverage, I'd rather not duplicate it.