beckn / beckn/logistics

Standard Enums for item categories.

Open
#9 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Instead of every participant creating their own item categories. It would make sense to use standardized product and service categories in the form of (HSN codes for products and SAC Codes for services). This way all participants would have a common language Also these codes have a universal acceptance across countries too.

https://cbic-gst.gov.in/gst-goods-services-rates.html

For E.g In Delivery BPP, we may have categorizations like Food, Books, Documents House hold items, Electronic items .... And every bpp may have their own categorization. This will have 2 issues. Users will not be able to query for a category as these codes are different by BPPS. And also same category would appear differently in the on_search from multiple bpps.

If we have a common enums of categories for logistic domain, it would help. This may be the issue with all domains but logging here and then once we have some methodology here, we can replicate for other domains.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the issue proposal and the linked CBIC GST goods-and-services rates page. Identify the logistics specification entry points where item categories are defined, then clarify the category scope, code source, and compatibility expectations with maintainers. Done means the project has an agreed standard-enum design and documented adoption criteria.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.