- What does answear/acs-bundle do?
- It is a Symfony bundle from Answear that integrates ACS pickup point data. It exposes ParcelShopsService::getList to fetch parcel shops for Greece or Cyprus, optionally filtered by shop kind, and returns ParcelShop DTOs. It is read-only discovery, not shipping labels, tracking, or rate quotes.
- Can I use answear/acs-bundle in Laravel?
- Not as a drop-in package. It is a Symfony bundle, so Laravel does not have bundle registration or Flex auto-registration. You can consume it in Laravel, but expect to build a thin adapter for configuration, service resolution, and DTO or exception mapping. Budget explicit integration work rather than a same-day composer require.
- How do I install answear/acs-bundle with Composer?
- The README uses composer require [email protected]:answear/acs-bundle.git, which is not a normal Packagist install. You will likely need a Composer VCS repository entry or a vendor fork or mirror, then pin a version for CI reproducibility. Verify repository access and package identity during supply-chain review.
- How do I configure ACS API credentials for answear/acs-bundle?
- Configure apiKey, companyId, companyPassword, userId, userPassword, and optional language, which defaults to GR. In Laravel map these to config/acs.php and environment variables instead of Symfony YAML. Verify keys against source because the README sample shows answear_gls and duplicates companyId while omitting companyPassword. Add config validation to catch silent misconfiguration.
- How do I fetch ACS parcel shops for Greece and Cyprus?
- Call ParcelShopsService::getList with a CountryIdEnum for Greece or Cyprus and an optional kind integer. The result is an array of ParcelShop DTOs. In Laravel wrap the service behind your own interface so checkout code does not depend directly on the bundle.
- What does the kind parameter do in ParcelShopsService::getList?
- The kind parameter is the ACS shop kind filter, and null means all kinds. Use it when checkout or a store locator needs a specific pickup point type. The valid integer values come from ACS documentation, so validate them in your application.
- How does answear/acs-bundle handle errors?
- The bundle throws ServiceUnavailable for Guzzle exceptions and MalformedResponse for incorrect payloads. That is adequate for a first release but coarse for retry, circuit breaker, or user-facing messaging policies. Map these exceptions to Laravel-friendly errors and add logging with context. Timeout support exists from version 2.1.1.
- Which Laravel, PHP, and Symfony versions are supported?
- The TPM notes PHP 8.4 and Symfony 7 requirements for current versions, with possible bundle 3.x or upgrades for older platforms. Check your Laravel version's Symfony component constraints before committing. Resolve a Composer matrix early because dependency conflicts are a medium risk.
- Is answear/acs-bundle suitable for production checkout delivery options?
- It can support checkout delivery-option discovery for Greece and Cyprus if you accept a thin adapter and validate the ACS contract early. It is not a complete logistics capability, so confirm scope is discovery-only. Also account for low adoption, Answear-internal ownership, and version pinning or forking for production use.
- Does answear/acs-bundle support shipping labels, tracking, or rate quotes?
- No. The bundle covers parcel shop and pickup point lookup only; it does not provide labels, tracking, returns, or rate quotes. If your roadmap needs those write-side carrier operations, you need additional ACS integration or another provider. Treat this package as an API-contract accelerator for discovery.